Skip to main content
Inspiring
July 22, 2025
Open for Voting

Moov Atom (Faststart) option when exporting in H.264

  • July 22, 2025
  • 2 replies
  • 95 views

So I recently stumbled into a bit of a rabbit hole around the moov atom in .mp4 files, basically a piece of metadata at the container level that tells the browser how to play the video.

I export all my videos using Adobe Media Encoder (not sure which version but i believe 2025 non beta), then upload them to BunnyCDN to use as direct .mp4 links for autoplaying videos on my Framer site. But I noticed that some videos, especially longer ones, just wouldn’t autoplay properly in Safari, while working fine in Chrome and Firefox.

After digging into it (and talking to Bunny), it turns out the moov atom needs to be at the start of the file for proper streaming and playback. Safari especially doesn’t like it when it's placed at the end, which, apparently, Media Encoder sometimes does without any way of changing it.

This is especially important for, as I understand it:

  • Autoplaying background/autoplaying videos on websites (like I’m building in Framer). Even though most videos of mine work, i suspect more than this one has the moov atom at the end, and they would probably load faster.

  • Safari, which is less forgiving and more prone to stalling

  • YouTube and other platforms that recommend faststart-optimized uploads

  • CDNs like Bunny.net, which optimize delivery around moov-at-start files (Their support said this directly to me)

I fixed it using FFmpeg and the -movflags +faststart command, which moves the moov atom to the beginning of the file without re‑encoding. That solved the problem.

But honestly, this feels like something that should be built into Media Encoder. Either as a default for H.264 exports or at least a visible checkbox somewhere. Right now, there’s no way to control it.

What’s more confusing is I found this old community post, where an Adobe dev said:

“Yes I can confirm that we always place MOOV atom at the beginning of the file (right after FTYP atom) when exporting to H.264 in MP4.”

But the video I just fixed was exported with Media Encoder and still had the moov atom at the end, causing all the playback issues in Safari.

Would love to see Adobe bring this back (or make it actually reliable).

2 replies

Inspiring
July 24, 2025

No sorry, I don't have a specific project file related to this, but I do have the video file that has the moov token in the end which was exported with media encoder if that would help you, not sure if there is meta information that could help you if thats what your thinking? As i mentioned i fixed a copy of that video file with ffmpeg. I had the video on my website for a while and just noticed as the main issue was the Safari touchpoint. But my render settings have always been 2 pass vbr with 20 , 20 bitrate depth. And all other settings has been more or less standard. But also checked maximum render quality and maximum depth checkboxes on. 

I also suspect a few more of my videos are also having its moov tag at the end. But dont have the same playback issue as they are way shorter in lengh, so safari in this instance fairly fast can load the moov token.

 

also another thought would be to be able to check files in say for example Adobe bridge to determine where the moov token is? 

EckiAME
Community Manager
Community Manager
July 24, 2025

If that is not happening it would be a bug. Do you have an example file for this with exact repro steps?