What video format works on a USB car stereo

Three constraints decide whether a car stereo plays a video from a USB stick. The safe target is an MP4 file containing H.264 video and AAC audio. Avoid HEVC (H.265) entirely, because head-unit chipsets made before roughly 2020 have no H.265 decoder at all. And if the stick is formatted FAT32, no single file can be larger than 4GB, whatever is inside it.

Most factory screens are small — 800x480 is common — so a 4K source is wasted bytes. Downscale to 480p and the file usually clears the 4GB wall by itself. The in-browser video converter on this site does all of it in the page, with nothing uploaded, for source files up to 2GB. A 6GB film is above what a browser tab can open at all, so that one belongs in the Android or iPhone app or in a desktop encoder.

The format to aim for

Head units are not media PCs. They run a fixed-function decoder block on a cheap SoC, and that block was specified once, when the unit was designed, and never updated. So compatibility is not about the file extension — it is about which codec is inside the container and whether the chip in the dashboard understands it.

If you do not know what is inside the file you already have, find out before you convert anything — you may only need a container change rather than a full re-encode. Drop it on the page and it will read back the container, video codec and profile, resolution, frame rate and audio codec, or read how to check a video's codec without installing anything for the longer explanation of what those fields mean.

Why HEVC is the single most common failure

H.265, also called HEVC, is what an iPhone records by default and what most 4K downloads use. It is roughly half the size of H.264 at the same quality, which is exactly why it spread so fast — and exactly why it fails in cars. HEVC decoding needs dedicated silicon. A head unit designed around a 2015 or 2017 SoC has an H.264 block and nothing else, so an HEVC file produces either "unsupported format", a black screen with working audio, or the unit simply skipping to the next file as though yours were not there.

There is no software workaround inside the car. The fix is to re-encode the video to H.264 before you copy it across, which is what the HEVC to H.264 converter does. That is a real re-encode, not a container swap, so it takes time and it is not lossless — but at a high quality setting the difference is invisible on a dashboard-sized screen. The same problem shows up on older desktops, which is why HEVC video refusing to play on Windows 11 is such a common complaint.

The 4GB wall, and what to format the stick as

FAT32 stores file sizes in a 32-bit field, so the largest file it can hold is 4GB minus one byte. This is a hard limit of the file system, not of the stereo. Copying a 6GB film to a FAT32 stick will fail during the copy on Windows and macOS alike, usually with a message about the file being too large for the destination.

You have two ways out. The first is exFAT, which has no practical size limit and which many units built in the last several years will read — but check your manual, because plenty of older head units list FAT32 or FAT16 only, and an exFAT stick simply reads as empty. NTFS support is rarer still. The second, and the one that always works, is to make the file smaller.

Smaller is usually the right answer anyway. A two-hour film at 480p and a moderate constant-quality setting lands comfortably under 4GB, and it will look no worse than the 6GB original on a panel the size of a postcard. Set the resolution to 480p in the advanced options and pick Medium or High quality; because the encoder works at constant quality rather than a fixed bitrate, a simple scene costs fewer bytes than a busy one and the file only gets as big as it needs to be.

When the picture plays but there is no sound

This is the second most common car-stereo complaint, and it is nearly always the audio codec rather than the video. Films distributed as MKV very often carry AC-3, E-AC-3 or DTS audio, because that is what a surround system wants. A head unit that decodes only AAC and MP3 will show the picture perfectly and stay silent.

Re-encoding the audio to AAC fixes it. In the converter's advanced options, set audio to re-encode rather than keep — that forces a fresh AAC track instead of copying the original stream through. The general version of this problem, including the cases where the audio stream is fine and something else is wrong, is covered in why a video plays with no sound.

The same file often has multiple audio tracks — an English track, a commentary, a dub. Only the first video and first audio stream survive a conversion here, and subtitle tracks are dropped. In a car that is a feature rather than a limitation: extra tracks are one of the things that make a head unit reject a file outright.

Making the file, step by step

1. Open the converter and drop your file in. Read the panel it shows you: container, video codec, resolution, audio codec.
2. Choose MP4 as the output.
3. If the video codec already reads H.264 and the audio reads AAC, the tool will tell you it is going to copy the streams. That takes seconds and the picture is bit-for-bit identical — it is only rewriting the wrapper. This is what happens with most MKV to MP4 conversions.
4. If it says re-encode, open the advanced options. Set resolution to 480p (or 720p for a larger aftermarket screen), frame rate to 30 or 24, and audio to re-encode.
5. Pick High quality if you have the time and Medium if you do not. The build is single-threaded, so a re-encode runs roughly at real time for 720p and slower for 1080p. A stream copy is near-instant no matter how long the film is.
6. Copy the result to the root of the stick, or to one plainly-named folder. Avoid deep folder trees and unusual characters in filenames.

Where a stream copy is available, take it — it is the only genuinely lossless option, and the reasoning behind that is worked through in converting MKV to MP4 without losing quality.

If it still will not play

Work through these in order, testing with a short clip each time rather than a two-hour film:

• H.264 profile. Very old units want Baseline profile, and a standard encode produces High profile. This converter has no profile switch, but its 3GP output is Baseline H.264 at 640px wide — ugly on a big screen, but about the most compatible file the tool can produce. Try that as a last resort.
• Variable frame rate. Phone recordings often have a frame rate that drifts, which can make a head unit stutter or desync audio. Setting an explicit frame rate in the advanced options converts it to constant; the mechanics are in converting variable frame rate to constant frame rate.
• The stick itself. Some units only read the first partition, dislike drives above a certain capacity, or limit how many files they will index in a folder. A small, freshly formatted stick with a handful of files is the fair test.
• Video is blocked while driving. Many head units refuse to show video on the main screen unless the parking brake is engaged. If you get audio and a message about parking, the file is fine and the unit is doing what it was designed to do.
• Rear-seat screens. These are often a separate decoder with separate rules. The same MP4/H.264/AAC target is still the right starting point.

The constraints here are close cousins of the ones on a living-room TV, where the container is usually fine and the codec inside it is not — if you are preparing the same films for both, converting MKV to MP4 for a smart TV covers the differences.