How to Set Up Separate Transcode Profiles for TVs, Phones, and Browsers

Eva Wong

IceWhale author

Eva Wong is the Technical Writer and resident tinkerer at ZimaSpace. A lifelong geek with a passion for homelabs and open-source software, she specializes in translating complex technical concepts into accessible, hands-on guides. Eva believes that self-hosting should be fun, not intimidating. Through her tutorials, she empowers the community to demystify hardware setups, from building their first NAS to mastering Docker containers.

How to Set Up Separate Transcode Profiles for TVs, Phones, and Browsers - Zima Store Online

A living-room TV, a phone on cellular data, and a browser do not report the same codec, subtitle, audio, or bandwidth capabilities. Treating them as one playback target causes avoidable video transcodes, burned-in subtitles, or streams that are too large for a remote connection.

Jellyfin does not provide a universal screen where an administrator names three arbitrary device profiles and forces every app into one. The reliable setup combines client playback limits, user policies, and server-side hardware acceleration, then verifies the decision shown in the playback dashboard for each representative file and network condition.

Build a Capability Matrix Before Changing Playback Settings

Choose one representative TV app, one phone app, and one browser, then record whether each can direct play your common video codec, audio codec, container, HDR format, and subtitle type. The Jellyfin client codec table is a useful starting point, but the actual device and app version remain the final test.

Use three known files: an ordinary 1080p H.264 title, your most demanding 4K HEVC title, and a file with the subtitle format your household actually uses. Note the source bitrate as well as the codec; a client may understand HEVC yet still request a lower bitrate over Wi-Fi or the internet.

Write the matrix before enabling more server features. It separates a genuine decode limit from a bandwidth cap or subtitle conversion, so later changes have a measurable reason instead of becoming a collection of guesses.

Playback class	Preferred path	Typical constraint
TV on LAN	Direct play	Audio and subtitle compatibility
Phone away from home	Capped transcode	Uplink and mobile data
Desktop browser	Direct stream or transcode	Browser codec support

Set the TV Baseline for Direct Play

On the TV client, leave quality at the highest stable local setting and enable audio passthrough only for formats the TV-to-receiver path can carry. A high local bitrate limit prevents the server from transcoding merely because the client advertised an unnecessarily low ceiling.

Prefer text subtitles such as SRT when possible. Image-based subtitles can force video transcoding on clients that cannot overlay them, even when the video and audio would otherwise direct play. Confirm the reason in the playback information rather than assuming hardware acceleration failed.

Keep the media path and server configuration easy to recover before tuning. The Jellyfin container pre-upgrade checklist is a practical reference for separating persistent configuration from replaceable container state.

Create a Constrained Mobile Path

Set the phone client remote quality to a bitrate your home upload connection can sustain with margin. Start below the measured upstream rate, because concurrent backups, calls, and other streams can consume capacity that a one-time speed test does not show.

Use a separate Jellyfin user for a family member when you need an administrative ceiling in addition to the client setting. User policy can restrict remote streaming bitrate or transcoding access, while the app still chooses a suitable resolution inside that boundary.

Test once on home Wi-Fi and once through cellular data. A stream that direct plays on the LAN but transcodes remotely is not automatically wrong; it is correct when the dashboard shows that bitrate, container, or codec conversion matches the mobile constraint.

-15% OFF

ZimaBoard 2 - Mini Home Server for Your Big Idea

Single board computer zimaboard2

Tune Browsers and Validate the Server Decision

Browsers vary by operating system and supported media formats, so test the browsers people actually use rather than promising one web profile. If a browser repeatedly transcodes a codec that a native app direct plays, installing the native client may be safer than weakening the whole library.

Enable and verify hardware acceleration only after the three client paths are defined. During a forced transcode, confirm that the expected GPU or media engine is active, the transcode directory has free space, and playback remains responsive under the number of simultaneous streams you expect.

The pass condition is explicit: the TV direct plays the baseline file, the phone stays under its remote bitrate, and the browser either direct streams or transcodes for a recorded reason. Stop and inspect logs if the same file chooses a different path after a client update.

Frequently Asked Questions

Can I Force One Jellyfin Profile by Device Name? Not reliably across all clients. Jellyfin clients report their capabilities, while client quality settings and user policies shape the result. Validate the chosen path in the server dashboard.

Why Does Enabling Subtitles Start a Video Transcode? The client may not support the subtitle format or may be unable to overlay it. Jellyfin then burns subtitles into the image, which requires video transcoding.

Should Every Remote User Share the Same Bitrate Limit? No. Base the limit on that user’s typical connection and your server uplink, then leave margin for other traffic and simultaneous streams.