About this site

editmp3tags.com is a free MP3 tag editor that runs entirely in your browser, made and looked after by one person. This page says who, why, and how.

Who

I'm Saurav Kumar Sharma, a software developer. I build small, single-purpose web tools: the kind that do one job on one page and don't ask you to sign up. This is one of a few dozen. It's a side project, not a company, and the only person answering the email address on the contact page is me.

Why it exists

I had a folder of MP3s with the wrong titles and a phone with no way to fix them. Every "online tag editor" I found wanted me to upload the file to their server first, which is a strange thing to ask for a job that takes a few kilobytes of arithmetic. Browsers can read and write files locally these days. So I built one that does the job on your device and never sees the file.

That's still the whole pitch. Drop a file in, fix the fields, download the corrected copy. No account, no upload, no queue.

How it's built

The site is plain HTML, CSS and JavaScript, hosted as static files on Cloudflare Pages. There's no server-side code and no database. Two open-source libraries do the heavy lifting: jsmediatags reads the existing tag, and browser-id3-writer writes the new one. The editor writes ID3v2.3 (with an optional ID3v1 copy) because that's what the widest range of players agree on; the how it works page lists exactly which frames are written.

You can check the "nothing is uploaded" claim yourself: load the page, disconnect from the internet, and edit a file. It works the same.

How it's funded

It's free to use and will stay that way. To cover hosting and the time it takes to maintain, the site may show advertising through Google AdSense. There are no paid tiers, no "pro" version, and nothing about your files is collected, because nothing about your files ever reaches me. The privacy page spells out what little the site does store in your browser.

How the guides are written

The guides are written by me, from two sources: the ID3 specifications, and experiments on real files. When a guide quotes a number, such as how many kilobytes a cover adds or what a tag looks like in hex, the number came from a test I ran and describe in that guide. When something is general knowledge about how players behave rather than something I measured, I say so. If you find a mistake, tell me and I'll fix it and note the change on the page.

No text on this site is generated by a tool and pasted in. The site does use a couple of open-source libraries, credited above, and one font family under the SIL Open Font License.

Get in touch

Bug reports, corrections and questions about tags are all welcome at thegeekpagesite@gmail.com. I read everything; I'm slower with feature requests than with bugs.