Reset to defaults
Need help?How to Convert M4R to WEBA
- Upload Your M4R Ringtone: Drag the
.m4rfile onto the page or click "+ Add Files". Batch upload is supported, so you can convert a whole set of notification sounds at once. - Choose Quality or Bitrate: WEBA output is encoded with Opus. Under File Compression, pick a Quality Preset, or set a Constant Bitrate, Variable Bitrate range, Custom Bitrate or Specific file size when you need a predictable size.
- Set Channel, Sample Rate and Trim (Optional): Audio Channel "MONO" suits short interface sounds. Trim lets you cut a long tone down to a one- or two-second ping before encoding.
- Convert and Download: Click Convert and save the
.weba. Files are uploaded over TLS, processed on our servers, and deleted automatically after a few hours. No sign-up, no watermark.
Turning a Ringtone into a Web Sound
An M4R is an iPhone ringtone: AAC-LC audio inside an MPEG-4 container, the same structure as an M4A, labelled with an extension that tells iOS it is a tone. Ringtones make good raw material for the web — they are short, loud and designed to grab attention, which is exactly what a chat notification, a "message sent" chime or a game alert needs.
WEBA is the audio-only flavour of WebM, the open media container Google introduced in 2010, based on Matroska. The audio inside is Opus, the codec the IETF standardised in 2012 as RFC 6716. Opus is royalty-free and efficient: at a given bitrate it generally holds up better than AAC, which lets you serve smaller files for the same perceived quality.
Two honest points before you convert:
- It is a second lossy generation. Your ringtone was already compressed with AAC. Re-encoding to Opus discards a little more. At a reasonable bitrate the difference is hard to hear, but the result can never be better than the source.
- You may not need it. Every major browser plays AAC in MP4, so if the goal is simply "make it play on my site", M4R to M4A gives you a web-ready file with no second codec. WEBA makes sense when you want Opus's efficiency, a royalty-free format, or a WebM-only toolchain.
M4R vs WEBA
| Property | M4R (input) | WEBA (output) |
|---|---|---|
| Container | MPEG-4, ringtone extension | WebM (Matroska-based), audio only |
| Codec | AAC-LC | Opus |
| Standard | MPEG-4 audio | Opus is IETF RFC 6716 |
| Licensing | AAC is patent-licensed | Royalty-free |
| Efficiency at low bitrates | Good | Better, especially for voice |
| Browser support | All major browsers | Chrome, Firefox and Edge; Apple support arrived late and varies by version |
| Typical length | 30 seconds or less | Any length |
| Best for | Ringing an iPhone | Notification sounds and audio on the open web |
Serving the Sound to Every Browser
Because Apple's browsers have historically been the weak spot for WebM audio, the robust pattern is to offer Opus first and an AAC fallback second. The browser picks the first source it can play:
<audio id="ping" preload="auto">
<source src="/sounds/ping.weba" type="audio/webm; codecs=opus">
<source src="/sounds/ping.m4a" type="audio/mp4">
</audio>
Make the WEBA here and the M4A on the M4R to M4A page from the same ringtone, and every visitor gets a sound.
Opus Bitrates for Web Sounds
Size in kilobytes is roughly bitrate (kbps) × seconds ÷ 8, so a short clip stays tiny even at generous settings.
| Use | Channels | Bitrate | 2-second clip | 30-second tone |
|---|---|---|---|---|
| Interface ping, click | Mono | 32 kbps | about 8 KB | about 120 KB |
| Spoken alert | Mono | 48 kbps | about 12 KB | about 180 KB |
| Musical jingle | Stereo | 96 kbps | about 24 KB | about 360 KB |
| Jingle with more headroom | Stereo | 128 kbps | about 32 KB | about 480 KB |
| High-bitrate source tone | Stereo | 160 kbps | about 40 KB | about 600 KB |
Encoding above the ringtone's own bitrate does not restore anything; it only avoids adding noticeable new loss.
Frequently Asked Questions
Will the WEBA sound worse than my ringtone?
Very slightly at most, if the bitrate is sensible. This is lossy-to-lossy, so some extra loss is unavoidable, but Opus at 96–128 kbps stereo, or 48 kbps mono for voice, is usually hard to tell apart from a typical ringtone.
Which bitrate is best for a notification sound?
For a one- or two-second mono sound, 32–48 kbps is plenty and keeps the file to a few kilobytes. For a musical jingle in stereo, 96–128 kbps preserves the character of the original.
Will the WEBA play on an iPhone or in Safari?
Not reliably on older Apple devices. Safari gained WebM support relatively late and Opus-in-WebM playback has varied between versions. Chrome, Firefox and Edge play WEBA without issue. Use the two-source <audio> pattern above, with an M4A fallback, to cover everyone.
What is the difference between WEBA and OPUS files?
The audio is the same codec in a different container. A .weba file wraps Opus in WebM, which browser media pipelines and WebM tools expect; a .opus file wraps it in Ogg, which standalone players and voice apps prefer. For a standalone file, use M4R to OPUS.
Can I use a WEBA file as a phone ringtone?
Generally not. iPhones use M4R for custom ringtones, and Android ringtones are usually MP3 or OGG. WEBA is a web delivery format; keep the original ringtone for your phone.
Can I convert the WEBA back into a ringtone later?
Yes, WEBA to M4R does that. Each extra lossy conversion costs a little quality, though, so it is better to keep the original .m4r than to round-trip it.
How are my files handled?
Files are uploaded over an encrypted (TLS) connection, converted on our servers, and deleted automatically a few hours after processing. The service is free, needs no account and adds no watermark. Other targets for your ringtone are listed on the M4R Converter.