Media diagnostics
Media codecs, containers, and browser support: diagnose before conversion
A media container is a wrapper. The video codec, audio codec, tracks, timing, and browser implementation inside it determine whether a local browser can preview, transform, or export a useful result.
On this page
A familiar extension is not a complete compatibility answer
MP4, MOV, WebM, WAV, and other extensions describe containers or file families, not every technical stream choice. Two MP4 files can have different video codecs, audio codecs, colour formats, subtitles, or metadata. One may play in a browser while another fails even though the filename looks identical.
Inspect the source facts first. A browser-local tool should surface unsupported inputs or constrained export choices instead of implying that every common extension can be converted safely in every browser.
Worked example: two MP4 files, two different paths
A short MP4 with a browser-supported H.264 video stream and AAC audio may preview and export through a straightforward local path. Another MP4 may contain a codec, profile, or timing feature that the current browser cannot decode. The identical `.mp4` suffix does not make their capabilities equivalent.
The useful result is a diagnosis: supported for this local operation, unsupported in this browser, or needs a different device or offline tool. A forced error-free interface that quietly drops a stream is less useful than an explicit limitation.
| Question | Example response | What still needs checking |
|---|---|---|
| What is the container? | MP4 or MOV file family. | Which codecs and tracks it carries. |
| Can this browser decode it? | Current local preview succeeds or fails. | Whether another browser or destination behaves the same. |
| Can it be re-encoded here? | A supported local output path is available. | Visual quality, sync, and destination acceptance. |
Browser capability is intentionally narrower than a desktop encoder
Browsers prioritize security, portability, battery, and their own supported media stack. A browser tool can be valuable for common local tasks while declining uncommon codecs, multiple tracks, or large files that would be better handled by a specialist desktop workflow.
Do not interpret a browser limitation as proof the source is corrupt. It may simply be outside the capabilities exposed by the current browser, device, codec installation, or memory budget.
Read compatibility outcomes as routing information
A successful result should still be played through to the end and compared for duration, audio sync, dimensions, and visible content. An unsupported result should preserve the source and tell you what information is missing, not encourage repeated lossy attempts.
For an external upload, verify the publisher’s current media rules separately. Browser support and destination support are two different compatibility systems.
Desktop tools and commands
Use a local tool