Free online M4R to 3GA converter

What the M4R format is

M4R is a filename extension associated with Apple ringtone files. It normally identifies an MPEG-4 audio file containing AAC audio, although the extension itself does not guarantee one specific codec. iPhone users commonly obtain M4R files through custom ringtone workflows involving Apple Music, iTunes, or GarageBand; files may also come from third-party ringtone sources or from an .m4a file renamed for ringtone use.

M4R is an extension, not a separate audio compression format. Renaming .m4r to .3ga does not convert the container or make the audio compatible.

What the 3GA format is

3GA is an audio-only 3GPP container, commonly created by Samsung Voice Recorder and older Android phones. It can contain AAC, AMR-NB, or AMR-WB audio. 3GA is useful on mobile hardware that expects the 3GPP container, while AMR encoding can produce very small voice-recording files and AAC generally provides better music quality at comparable listening levels.

3GA is not automatically more compatible than M4R. The receiving device may support only a particular codec, sample rate, number of channels, or bitrate, so its specifications determine the correct output settings.

How to convert the file

For a conversion without installing software, use the converter on 101convert.com. Upload the M4R file, choose 3GA as the output format, start the conversion, and download the resulting file. Uploading sends the source to a remote service, so do not use this method for private recordings unless its handling policy is acceptable.

For local, repeatable conversions, FFmpeg provides direct control. Install FFmpeg from a trusted package source, open a terminal in the folder containing input.m4r, and run:

ffmpeg -i "input.m4r" -map 0:a:0 -c:a copy -f 3gp "output.3ga"

This remuxes the first audio stream into a 3GPP container without re-encoding it. If the M4R contains AAC supported by the destination device, this avoids additional audio quality loss. The 3gp muxer is used because 3GA is an audio-only 3GPP file; the .3ga extension identifies the intended file type.

If the device rejects the copied AAC stream, encode a new AAC stream during conversion:

ffmpeg -i "input.m4r" -map 0:a:0 -c:a aac -b:a 128k -ar 44100 -ac 2 -f 3gp "output.3ga"

This setting suits many modern mobile players, but it re-encodes the audio and can reduce quality. Match the source sample rate and channel count when possible; forcing stereo does not improve a mono ringtone.

For an older device that explicitly requires AMR-NB, use an FFmpeg build containing an AMR-NB encoder:

ffmpeg -i "input.m4r" -map 0:a:0 -c:a libopencore_amrnb -ar 8000 -ac 1 -b:a 12.2k -f 3gp "output.3ga"

AMR-NB is intended mainly for speech and produces lower fidelity than AAC for music. If FFmpeg reports that libopencore_amrnb is unavailable, install a build with that encoder or use AAC if the target device supports it.

Quality and compatibility limits

• Remuxing is not re-encoding: the first FFmpeg command changes the container while preserving the encoded audio stream. The AAC command and AMR command decode and encode the audio again.
• Metadata may be lost: ringtone artwork, embedded cover images, and some Apple-specific metadata usually do not transfer to a basic 3GA file. The audio itself is selected explicitly with -map 0:a:0.
• Device restrictions matter: some older phones accept only AMR-NB at 8 kHz mono, while others accept AAC in a 3GPP container. Check the device manual if the converted file will not play.
• Protected sources may fail: DRM-protected audio cannot normally be converted by FFmpeg or a standard converter. Use an unprotected copy that you are authorized to convert.
• Ringtone behavior is separate from playback: converting the file may make it playable, but a phone can still require a specific folder, filename rule, duration, or ringtone-import procedure.