Album Art Done Right: Embedding, Sizing, and Sourcing Covers
Album art done right: embedded covers vs folder.jpg, the resolution sweet spot, where to source high-quality artwork, and tools to keep it consistent.
Album art done right: embedded covers vs folder.jpg, the resolution sweet spot, where to source high-quality artwork, and tools to keep it consistent.
You know the gray square. You're scrolling your library, everything looks like a record shop wall, and then: a blank placeholder where a cover should be. Or worse: a smeary 200-pixel thumbnail, blown up to fill the screen, artifacts and all. The music is pristine lossless; the artwork looks like it was faxed.
Album art is the most visible part of your library (it's literally the interface you browse) and it's also the part collectors most often leave to chance. The fix isn't complicated, but it does involve three real decisions: where the art lives, how big it should be, and where to get copies worth keeping. Let's take them in order.
There are two places a cover can live, and they solve different problems.
Embedded art is stored inside each audio file itself, a PICTURE block in a FLAC, an APIC frame in an MP3's ID3 tag. Its superpower is portability: the image travels with the file. Copy one track to a phone, hand an album to a friend, drag a file into a browser player, the cover arrives too, no questions asked. If art is embedded, it works everywhere, full stop.
Folder art is a single image file sitting next to the tracks, conventionally cover.jpg or folder.jpg in the album folder. Its advantages are the mirror image: one copy per album instead of one per track, trivially easy to replace or upgrade, and visible in file browsers. Its weakness is that it stays behind whenever a file travels alone, and different players hunt for different filenames.
So don't pick a side. The battle-tested policy is:
cover.jpg in each album folder: this is your archival master, ready for whatever screen sizes the future brings.Embedded art is for playback; folder art is for posterity. Two copies, two jobs.
The one honest cost of embedding: duplication. A 300 KB cover embedded in twelve tracks is ~3.6 MB per album, a rounding error next to the FLAC audio, but a reason not to embed multi-megabyte scans in every file across thousands of albums.
The eternal tradeoff (resolution versus file size) has a comfortable middle, and it's wider than people think.
For embedded art, somewhere around 1000 to 1500 pixels square is the sweet spot. It's crisp on phones, laptops, and most desktop views, yet a JPEG at quality ~85–90 lands in the 100–400 KB range, cheap enough to embed everywhere without thinking. Below about 600 pixels, covers start looking soft on modern screens; that was the standard once, and libraries built to it now look dated.
For the folder copy, keep the best you can get: the original 3000-pixel store download, your own scan, whatever. Storage is cheap and you only keep one per album. If you ever want bigger embedded art later, you regenerate from these masters, never the other way around; upscaling a small cover just makes a bigger blurry cover.
Format-wise, JPEG is the right default for covers: they're photographs and paintings, which JPEG compresses beautifully. PNG earns its bloat only for flat graphic artwork with hard edges and text. And a practical footnote: some older hardware (car head units, vintage DAPs) is fussy about very large images or progressive JPEGs, so plain baseline JPEG at sane sizes is the compatibility play.
The art is only as good as the copy you start from. In rough order of preference:
What to avoid: random image-search results. They're routinely upscaled, recompressed, watermarked, or (subtly worse) the wrong version: the remaster cover on your original pressing, the censored variant, the streaming-era redesign. Part of owning a specific edition of an album is keeping its actual face.
Like everything in library-keeping, the value compounds only if the policy is uniform. A library where half the albums have embedded art behaves like a coin-flip every time you hit play. So write the rules down once:
cover.jpg, lowercase, done.Tooling makes the uniformity nearly free. MusicBrainz Picard embeds fetched art as it tags. Mp3tag batch-embeds, extracts, and replaces covers across whole trees. foobar2000 can report which albums are missing art and fix them in bulk. A consistent folder structure is what makes those batch operations trivial: one album per folder, one cover per album, no exceptions to trip over.
Here's a nice way to check your work: modern browsers read embedded art straight out of the file. Open the player, drag an album in, and the cover should bloom onto the screen instantly: no internet lookup, no scraping, just your file describing itself. If you see the gray square instead, you've found tonight's small project.
Covers are the part of a collection you see every single day. The audio took care of itself the moment you went lossless; give the artwork the same respect once, and every future scroll through your library looks like the record wall it deserves to be.
FLACCID plays your local FLAC, ALAC, WAV and more right in the browser: no upload, no account, no streaming.
Launch the Player