You open a folder and see cropped cropped sludgeblack 1 2 png. That's not a release title. It's a working file—usually the leftover of a cover scan, a flyer photo, or a web image that went through two separate cropping steps before someone slapped on a genre tag and a sequence number. In the underground, files like this travel through email attachments, cloud folders, and small label sites. Decoding that string can save you from mislabeling a tape or sending a printer a file that will come out as a black square.
What the File Actually Is
The filename tells a story—a record of how it was handled. Each token was added by a person or software, and the order reveals the steps.
The first token, cropped, is the kind of suffix image editors append automatically when you export a selection. The second cropped means the file was exported from an already cropped version. That happens often in DIY production: someone scans a J-card, crops it for a Bandcamp square, then crops that square again for a social media post or distro sheet. Result? A file at least two generations removed from the original scan.
The middle token, sludgeblack, is a genre compound. Not a formal category—it's a sorting label downloaders and distro owners use to keep files organized. It points to music that draws on sludge metal and black metal, but the tag says more about the person who named the file than about the music itself.
The final token, 1 2, is the murkiest part. The space suggests two separate values. Could be page 1 of 2, side 1 of 2, or a position in a two-image set. Might be leftover from a contact sheet or a file count. Without the original directory, the sequence is unreadable. That same ambiguity shows up in numeric codes on Japanese cassettes; a separate post on this blog looks at the meaning of '3 2' on Japanese underground cassettes.
The .png extension tells you the file uses lossless compression. Good for text and hard edges, but it doesn't mean the image is high quality. A PNG made from a heavily compressed JPEG just stores the same artifacts in a larger file. PNG also supports transparency; if the file has an alpha channel, printing it without flattening can produce white or black boxes.
How to Read a Filename Like This
The table below separates the filename into its components and shows what each part can and cannot tell you.
| Part | What it tells you | What it does not tell you |
|---|---|---|
| cropped cropped | Two export or crop steps | Original dimensions or source |
| sludgeblack | Genre tag used for sorting | Artist, label, or release date |
| 1 2 | A sequence or page count | Which side comes first |
| .png | Lossless container | Whether the image is print-ready |
The Genre Tag Is a Shelf Label
Genre compounds like sludgeblack are common in underground file sharing because they're compact. A single word can place a release next to other files with a similar sound. But the same word can mean different things in different scenes. One listener uses sludgeblack for slow, distorted black metal; another uses it for blackened sludge with a hardcore base. Neither is wrong—the tag isn't a definition. It's a local agreement between the person who named the file and the person who will find it later.
For a collector, the tag is useful for search but not for description. If you're building a database, keep the filename tag as a keyword, but don't let it replace your own listening notes. The artist or label may describe the same release as noise, drone, or something else entirely. The filename only records how it was filed.
In Japanese underground distribution, English genre tags are common because distro lists are read by international buyers. A file named sludgeblack may come from a Japanese distro, but the tag doesn't mean the artist identifies with that term. It's a bridge for shipping, not a manifesto.
The Numbers Are Not a Code
Numeric suffixes in filenames are easy to over-read. In the file 1 2, the space matters. A file named 1_2.png would suggest a track position or catalog number; 1 2 reads more like a page count or side indicator. But without the rest of the folder, the numbers can't be decoded.
That's different from the intentional numbering on Japanese underground cassettes, where codes are often printed on the shell and J-card. Those codes are meant to be read. A filename suffix is usually whatever the export dialog produced. Treat it as a hint, not a key.
PNG, TIFF, and the Limits of a Crop
PNG is reasonable for web images and small print jobs, but it's not an archival format. Archival scans are usually saved as TIFF or uncompressed PNG with no cropping. That distinction matters when a label wants to reprint a cassette or a collector wants to preserve a scan for the future.
Cropping removes pixels permanently. Saving a cropped image as PNG doesn't restore them. The file size may be large, but the information outside the crop is gone. If you have the original scan, keep it separate from the web version. If you don't have the original, the cropped file is still useful, but mark it as a derivative.
How to Check Whether a PNG Is Print-Ready
A PNG can look sharp on screen and still fail on paper. First check: pixel dimensions. For a standard cassette insert, a 300 dpi scan of a 10×15 cm J-card needs roughly 1181×1772 pixels. A 400×400 file won't cut it for a reprint.
Second check: alpha channel. If the image has transparency, the printer may render the transparent area as black or white. Flatten the image onto a background before exporting a print file.
Third check: color. A PNG saved from a web browser is usually in sRGB. Fine for many short-run cassette plants, but if the label asks for CMYK, convert in a proper image editor and keep a copy of the original RGB version.
Finally, check the embedded resolution. PNG stores resolution in a pHYs chunk, but many export tools omit it. If the file opens at 72 dpi, the print size will be much larger than intended. Set the resolution to 300 dpi in an image editor before sending to a plant.
What to Do with a File Like This
If you find a file with this kind of name in a download folder, a label email, or a distro zip, treat it as a draft—not the final master. These steps are simple but they prevent permanent loss.
- Copy the file before renaming it. The original name is evidence of the workflow.
- Open it in an image editor and check the pixel dimensions, color mode, and alpha channel. A 400×400 PNG is fine for a web preview, but useless for a printed insert.
- If you plan to print, flatten the image and export a PDF with bleed. Don't send a cropped PNG to a cassette duplicator.
- Rename the file with a descriptive scheme: artist, release, page, and source status. A name like 2023-06-15_label_cat_cover_scan.png is more useful than cropped cropped sludgeblack 1 2 png.
Why the Original Matters
A cropped image is a fragment. For a collector, a scan of a J-card with the original margins intact is more useful than a tight crop. The margins often hold the label's address, catalog number, and mastering credit. Cropping them away to make the image look better for a post destroys information. A double crop makes the loss worse—the second crop removes whatever context survived the first one.
For labels, the lesson is to keep masters. When preparing a digital release, export a full-resolution PNG or TIFF of the cover before cropping for social media. Name the master file with the catalog number, not with the word cropped. The file that gets uploaded to a distro should be as close to the original scan or design file as possible.
The filename cropped cropped sludgeblack 1 2 png is not a failure. It's a normal object in a culture that values speed over polish. But if you treat it as a final artifact, you lose the context that makes underground music documentation useful. No amount of sharpening will bring back the missing pixels.
So next time you see that string, don't just double-click. Open it, check the dimensions, rename it something useful. That filename is a clue, not a label.