Your music stays with you

Taglet is built so it never needs your files. Reading, converting, tagging, cropping and zipping all happen inside your browser, on your device.

What happens on your device

When you add a song, your browser reads it straight from your disk. Taglet uses ffmpeg, compiled to WebAssembly, to read tags and convert audio. The first time you add a file, your browser downloads that engine (about 10 MB compressed) from taglet.net and keeps it, so it works offline afterwards. Cover art is cropped on a canvas in the page. Finished files are handed back to you as a download or through your device’s share sheet.

None of this sends your audio, art, titles or file names anywhere. You can check: open your browser’s network tools while you convert, and you’ll see no uploads.

Linking a device

Link a device is the one feature that moves files over the internet, and only when you send something. The pairing code is turned into an encryption key on each device. Files are encrypted with AES-GCM before they leave, pass through a small relay on Cloudflare, and are decrypted on the other device. The relay sees only a scrambled room name and encrypted bytes. It can’t read them and stores nothing. The code is part of the QR link after the #, which browsers never send to a server.

What we don’t do

• No accounts, no sign-in.
• No analytics, tracking pixels, ads or third-party scripts.
• No cookies. Your accent colour is kept in your browser’s local storage, and that’s all.

Hosting

taglet.net is served by Cloudflare. Like any web host, Cloudflare handles standard request data such as IP addresses to deliver pages and stop abuse. Taglet doesn’t log or keep it.

Questions

Taglet is a project by Stevie McLane. The code is open on GitHub, so you can read exactly what it does.

Last updated November 2026.