Getting music your car stereo will actually play

They loaded a USB stick and the car skipped every track, or showed nothing at all. The problem may be the format, but it is just as often the filesystem, the folder depth or the file names — and no guide covers all three together.

Make the stick MP3, 44.1 kHz, stereo, constant bitrate at 192 or 256 kbps, on a FAT32 USB drive, with plain ASCII file names in shallow folders. That combination plays in essentially every head unit built since the mid-2000s, factory or aftermarket. If your car skipped every track or showed No Media with a stick full of music, the format is only one of four suspects — the filesystem, the folder structure and the file names cause just as many failures, and they produce exactly the same silence. Work through them in that order and you will usually find the real one within a couple of minutes.

The combination that always works

A head unit is a cheap embedded decoder with a fixed feature list burned in at the factory. It does not update and it rarely says what went wrong, so the target is not the best-sounding file. It is the least surprising one.

• MP3, because it is the only format that is genuinely universal. Everything else is a bet on the model year.
• Constant bitrate, 192 or 256 kbps. A car is a noisy room. In one, most people cannot separate 192 kbps from the source, and the extra bytes buy you fewer tracks per stick rather than more detail. 320 is the ceiling the MP3 format allows, not "CD quality" — a CD is 1,411 kbps and uncompressed.
• Why constant rather than variable: older units read the first frame header and assume every frame matches, so a VBR file shows the wrong track length and seeks to the wrong place. Newer units read the Xing/LAME header and cope. CBR sidesteps the question.
• 44.1 kHz. 48 kHz is usually fine; 88.2 and 96 kHz are refused by a lot of hardware that is otherwise perfectly modern.
• ID3v2.3 tags, not v2.4. A good number of units read v2.3 only and show a blank title for anything else. Keep embedded artwork small; some systems stall browsing folders stuffed with two-megabyte cover images.

What head units support, roughly by era

There is no standard here, only convention. Treat this as a starting guess and check the manual for your model; the supported-formats page is usually near the back, under Specifications.

WMA in the older rows is an artefact of the period: Windows Media Player ripped to WMA by default for years, so car makers licensed the decoder. If the newer car in the driveway will not touch that old library, convert WMA to MP3 rather than re-ripping the discs.

When it is not the format at all

Four failures produce the same symptom as an unsupported codec.

The filesystem

Most head units mount FAT32 and nothing else. exFAT works in a fair share of post-2015 systems, NTFS in almost none. A 64 GB or 128 GB stick arrives formatted exFAT from the factory, which is why a new drive that works perfectly on a laptop reads as empty in the car.

Reformat it. On Windows, right-click the drive in File Explorer, choose Format, and pick FAT32 if it is offered. On a Mac, open Disk Utility, click View > Show All Devices, select the physical drive rather than the volume beneath it, choose Erase, set Format to MS-DOS (FAT) and Scheme to Master Boot Record. One partition, not two.

Folder depth and file counts

Published limits vary by manufacturer, but the shape is consistent: something like eight levels of nesting, a few hundred files per folder, and a ceiling on total indexed tracks. Deep Music/Artist/Album/Disc 1/ trees from a media server hit those walls quickly. One flat Artist - Album folder per album, at the root of the stick, avoids all three.

File names

Stick to letters, numbers, spaces, hyphens and underscores. Accented characters, question marks, slashes and non-Latin scripts are the classic cause of a unit that plays nine tracks and skips the tenth. Keep names short, too: many displays truncate hard.

The port itself

Some USB sockets in cars are wired for charging only, and some supply too little current for a large drive. If a small old stick works where a new one does not, that is what you are looking at. Try a different port before blaming the files.

Why the tracks play in the wrong order

Many head units do not sort at all. They read the FAT directory table and play entries in the order they were physically written, which is the order your computer happened to copy them in. Often alphabetical by chance, rarely so once you have deleted a track and added another.

Three fixes, in ascending order of effort:

1. Number the file names. 01 - Track.mp3 through 12 - Track.mp3. Use a leading zero, or track 10 sorts before track 2 on any unit that does sort by name.
2. Copy in order. One album folder at a time, selecting the tracks in order rather than dragging the folder in one gesture. Tedious, but it satisfies the units that respect write order.
3. Sort the directory table. Tools exist that rewrite the FAT entries in alphabetical order without moving any data — DriveSort on Windows, fatsort on Linux and macOS. Run one after the copy finishes and the problem disappears permanently, including on units that ignore file names entirely.

Converting a whole library, honestly

A library is a batch job, and this site's converter handles one file at a time in your browser tab, so it is the wrong shape for a thousand albums. It is the right shape for the stragglers you find afterwards: the four tracks the car skipped, the podcast episode that arrived as .m4a. Converting a stray M4A or a FLAC album takes a moment per file and never leaves your machine.

For the whole library, use a real batch converter:

• Windows: foobar2000 is free and its Convert dialog writes the output into a mirrored folder structure with names built from the tags. fre:ac is a simpler free alternative; dBpoweramp is paid, and the one most rippers settle on.
• macOS: XLD is the free standard. The Music app can also do it — set Settings > Files > Import Settings to MP3 Encoder, then select the tracks and choose File > Convert > Create MP3 Version.
• Either: point the batch tool at a copy of the library, not the library itself.

Set the encoder to CBR 192 or 256 and let it run. A large library takes a while whichever tool you use: MP3 encoding is real work, not a rewrap, and no converter can make it otherwise.

FLAC and M4A in newer cars

If your unit lists FLAC in its manual, use FLAC and skip the conversion — it decodes to exactly the samples that went in. Two caveats. Support usually stops at 16-bit, 48 kHz, so a 24-bit/96 kHz download may be refused by a unit that plays ordinary FLAC happily. And FLAC runs roughly five to six times the size of a 256 kbps MP3, so a stick that held the whole collection will hold a fraction of it.

M4A is the middle case. Anything from about 2015 onwards usually plays it, and most phone recordings and Apple downloads are already M4A, which saves a step. Going M4A to MP3 means decoding one lossy file and re-encoding it as another, and the second encoder cannot put back what the first threw away — read how the two formats differ before converting a library that is already fine.

One thing no stick can carry: tracks downloaded inside a streaming subscription are encrypted containers rather than audio files, and they cannot be copied onto a USB drive or converted by anything, here or elsewhere.

Keep the originals

Convert into a separate folder — Car USB on the desktop is fine — and copy the stick from there. Never let a converter overwrite the library in place.