The Plex preroll format I'd actually use (and why it isn't ProRes)

I used to deliver everything at the highest spec I could, until a customer explained what it was doing to his remote streams. His complaint had nothing to do with how the intro looked. It was about the wait after it, and frankly he had a point.

A preroll lasts a few seconds.

Nobody pauses on the third second to admire the detail in a studio globe. What people do notice is a spinner sitting between the logo and the film, and a heavy file is one of the easiest ways to put one there. So the Plex preroll format I'd pick for most servers is a dull one: 1080p, H.264 video, in an MP4 container. 4K is fine in particular rooms. ProRes doesn't belong anywhere near a Plex client and I'll get to why in a minute.

Getting the file into Plex

Adding a pre-roll to Plex takes a minute. Open the server settings, go to Extras and paste the full path to each video into the "Cinema Trailers pre-roll video" field. Commas between files play them all in order and semicolons make Plex pick one at random. Leave out any spaces around the separator. Then switch Cinema Trailers on in the app and in the library's advanced settings.

That's all from Plex's Extras page. What's oddly missing from it is any word on format. There's no codec or container list and nothing about resolution, so the only clue is that the example paths end in .mp4 and .mkv. I don't read that silence as "anything goes". I read it as Plex assuming you'll hand it the same kind of file you'd give it for a film off a disc or a download, which is pretty much the right assumption anyway.

The same page says not every Plex app supports Cinema Trailers. So a preroll can work on the box under the television and never show up in a browser. That's worth ruling out before anyone re-encodes anything.

Why ProRes is the wrong file here

ProRes is lovely to cut with, and that's the job Apple built it for. The ProRes white paper pitches it as a codec for high quality editing in Final Cut Pro, and the data rates show what that costs: about 176 Mbps for ProRes 422 HQ at 1080p and 24 frames a second, and about 707 Mbps for the same thing at 3840x2160. Even ProRes 422 Proxy, the lightest flavour, sits around 36 Mbps at 1080p.

That's a lot for a logo. Now put those numbers next to a remote stream. Plex's bandwidth settings page says the server only uses 80 percent of the upload speed you enter, so a home line with 20 Mbps up has roughly 16 Mbps to give every remote viewer combined. The Proxy file wants more than double that on its own. The HQ master wants about eleven times as much (and the 4K one I'd rather not think about). None of that goes out untouched, so the server transcodes it, and it has to start in the very first second of playback when there's no buffer built up and nothing on screen except black.

Jellyfin's codec tables don't mention ProRes at all. It isn't in the supported column or the unsupported one. For a file that's meant to reach a living-room client, I'd call that a fairly loud hint.

4K depends on who's watching

A 4K library doesn't automatically make a 4K preroll sensible. Someone watching locally on a 4K television with a decent streaming box may have no trouble with a 4K HEVC file, and on a big screen the extra sharpness in a logo is real. Hand the same file to a laptop browser or an older box and it's a different story. Jellyfin's own table notes that Roku only decodes HEVC on its 4K models, and HEVC support in Chrome, Edge and Firefox depends on the device. Plex clients aren't identical to Jellyfin's, but the hardware underneath them is the same hardware.

The opposite mistake is much milder. A 1080p preroll on a 4K screen might look a bit softer than the film that follows it, and that's about the worst of it. I'd take a slightly soft logo over a sharp one that holds the film hostage.

So for a library that's mostly watched at 1080p, or one with regular remote viewers, I'd use 1080p H.264 in MP4 and stop worrying. For a cinema room where every client is known to play 4K directly, a 4K copy can earn its place, as long as it's been tried on the weakest device in the house and not only on the newest one.

Direct Play is the part that decides it

Plex's Direct Play documentation is clear about what has to line up for a file to play unchanged: container, codecs, bitrate and resolution, all of them compatible with the client. If only the container is wrong, Direct Stream repackages it on the fly. A bad video stream means a full transcode, which is the expensive one and exactly what you don't want for a file that runs for a few seconds before the film.

Resolution gets all the attention, but it's one of four. A 1080p file can still get transcoded because of its audio track, while on the right television a 4K file sails through.

When a preroll misbehaves I look at the whole playback path before blaming the animation, and my guide to every cause of a Plex preroll not working goes through the settings side of it in order.

Timing makes all of this feel worse than it is with a film. Mid-film it barely registers. A transcode there usually settles after a few seconds and you forget it happened. With a preroll the server starts on one short file and then has to switch to the main title. I suspect that hand-off is where a lot of the "Plex is broken" feeling comes from, though there's no public explanation from Plex of how it schedules the switch. People were asking on the Plex forum back in February 2019 for the film to start buffering while the pre-roll plays, and the thread was still getting replies in June 2020.

The Universal globe at 1080p

Universal is a good case because the globe and the star field around it are the kind of fine detail 4K flatters. It's tempting to treat a studio ident like that as a showpiece that deserves the biggest file in the folder. I'd resist that.

When someone asks me for a custom Universal 100th anniversary intro, the first thing I'd want to know is where it's going to play. A home cinema with local 4K files and one known box is one answer. A server shared with a sister's phone and a laptop in another city is another, and I'd guess it's the more common setup, honestly. The animation can stay cinematic either way. Only the delivery file changes.

That's the question I'd put first for any of the intros I make at Priyansh Animations, Universal or not.

If you do keep both, a 4K copy for the cinema room and a 1080p one for everyone else, don't put them in the Extras field separated by a comma. Plex plays comma-separated files one after the other, so the lounge gets the globe twice.