Free · no sign-up · nothing leaves your phone
YouTube to MP3 Converter — size & download-time planner
Before you pull a track offline, find out exactly what it costs you: how many megabytes a 3-minute song eats at 192 kbps, and how many seconds of your connection it takes to fetch. Change one number and the answer updates instantly.
3:45 at 192 kbps → 5.1 MB · 2.2 s on 20 Mbps
Plan your download
Everything is computed in your browser — no upload, no waiting, no server round-trip.
Data cost at every bitrate
The same audio at all six MP3 bitrates, using your current track length, track count and speed. Tap a bitrate above to switch the plan.
How it works
Three numbers decide everything: how long the audio is, how many bits per second you keep, and how fast your connection pulls bytes in.
MP3 size is simply duration × bitrate. One second at 192 kbps is 24 KB, so a 3:45 track lands near 5.1 MB.
Total megabytes are turned into megabits and divided by your Mbps figure, giving honest seconds instead of a vague promise.
Each bitrate carries a plain-language verdict, so you can trade a little fidelity for a lot of saved data.
Built for metered data plans
No submit button. Type a length, pick a bitrate, and both cards re-render on the same keystroke — under 100 ms, no server round-trip.
Arabic-Indic digits (٠-٩), Persian digits and the Arabic decimal separator are normalised to plain ASCII before parsing.
Blank or zero speed falls back to 20 Mbps and the card says so, so you always get a usable answer instead of an error.
Anything under 0.1 MB is shown in KB, so a 9-second clip at 64 kbps reads 77 KB — never a misleading 0.0 MB.
FAQ
How big is a 3-minute MP3 at 192 kbps?
About 4.3 MB for exactly 3:00. The default 3:45 in the planner comes out at 5.1 MB, because size scales linearly with time and bitrate.
Should I pick 128 or 192 kbps on mobile data?
128 kbps is the usual compromise: noticeably smaller files and hard to fault on phone speakers. Choose 192 kbps when you plan to listen on decent headphones, or 64–96 kbps for talk, podcasts and audiobooks.
Why does the download time differ from the app I use?
Converting and fetching are different steps. This planner times the transfer of a finished file at your line speed; real-world speeds dip on congested cell towers, and the host service adds its own conversion time.
Is anything uploaded?
No. Every calculation runs in your browser with plain JavaScript. There is no account, no cookies needed for the math, and no API call.
What does "transparent for most listeners" mean?
It means that in listening tests most people cannot reliably tell the compressed file from the source. 192 kbps hits that bar for typical pop and rock; 320 kbps is where the difference disappears even on studio gear.