Some unprotected M4V files are already MP4-format videos with a different extension. If you can confirm that and the destination accepts their codecs, renaming a copy to .mp4 may be enough. Otherwise, rewrap compatible streams or encode an H.264 MP4 copy. A protected store download is a different case: ordinary converters cannot turn it into an unrestricted video simply by changing its name.
Identify the M4V before choosing a method
Check where the file came from. HandBrake’s own documentation describes its .m4v outputs as MP4 files under another extension. That scoped statement does not establish the format or protection status of every file named .m4v. An extension can also be misleading or refer to a raw video stream.
Open an unprotected source in Shutter Encoder and use File(s) information to examine the container and video/audio tracks. Codec inspection alone does not prove a file is unprotected; use the source’s provenance and playback restrictions as well.
| Your file | Approach | Why |
|---|---|---|
| Verified unprotected MP4-format M4V with accepted codecs | Rename a copy | Only the filename restriction needs changing. |
| Unprotected media with compatible streams | Rewrap to MP4 | The tool writes a proper output container. |
| Unsupported video or audio codec | Encode a compatibility copy | Repackaging cannot change codec support. |
| Protected purchase or rental | Use the authorized playback or export options | An ordinary converter is not a DRM-removal workflow. |
Rename only a confirmed compatible copy
- Duplicate the verified unprotected file. Keep the original M4V.
- On Windows, show filename extensions in File Explorer; on Mac, show the full filename in Finder or Get Info. Change the copy’s final .m4v suffix to .mp4, accepting the extension-change prompt.
- Make sure the name is not accidentally clip.mp4.m4v. Open the copy in the destination and check audio, seeking and duration.
- If the destination still refuses it, read the error and use a rewrap or encode instead. Renaming again cannot change the video codec.
This limited filename workaround should not be applied to MOV files or arbitrary video formats.
Write a new MP4 with Shutter Encoder
For an unprotected input whose codecs already suit the target, add it to Shutter Encoder, choose Rewrap → .mp4, set a separate output folder and start the function. Check the resulting file and required tracks. If rewrapping fails because a stream is unsupported, do not force an extension change.
When the destination requires H.264, follow the HandBrake MP4 encoding steps. Inspect the audio and subtitles rather than assuming a new container keeps all of them. If the source uses HEVC, the HEVC guide explains the codec change.
Problems that renaming cannot solve
- Authorization or protected-playback message: return to the provider’s supported application.
- Video but no sound: the destination may reject the audio codec; choose supported audio when making a new copy.
- Missing chapters or subtitles: verify the output track list and app support.
- Input cannot be identified: obtain a complete source copy and inspect its actual format before converting.
Common questions
Is renaming M4V a lossless conversion?
Renaming does not process the media at all. For a verified MP4-format source, it can solve an extension check, but it is not a container conversion or a quality improvement.
Can HandBrake export an MP4 with an M4V extension?
Yes. Its container documentation describes that naming behavior. Check the output container and codecs rather than deciding from the suffix alone.
Sources & method
Prepared by Videmovo · October 11, 2026. Researched from the documentation below; these are not hands-on conversion tests. Application support, interfaces and service conditions can change.
- HandBrake: containers and its MP4/M4V naming convention (draft documentation) ↗
- Shutter Encoder: functions, outputs and audio settings ↗
- HandBrake: opening, presets, destination and encoding ↗
- HandBrake: supported sources and copy-protection limits ↗