Something in the middle decided this was small enough

One file row, printed small, at the size you'd actually read it.

A plain rectangular box with a diagonal line through it, where a preview would normally sit.

Beside the box, scan_0043.jpg, and under that, smaller and in dulled orange, 41 KB.

A hairline rule runs beneath. Nothing else is on the shirt.

What does the crossed-out box mean?

It's the universal placeholder for a picture that should be there and isn't rendering.

Every viewer that handles images draws some version of it — a plain frame with a line through the middle, standing in for content it either never received or couldn't decode. It's not decoration; it's an apology built into the interface, printed automatically whenever an expected picture fails to arrive. Seeing it here, on its own, with no image ever having loaded around it, is the whole design stated in the most literal way it could be.

Why does 41 KB tell the whole story by itself?

Because a scanned page has an expected weight, and 41 KB is far under it.

A scan carries enough detail to be worth calling a scan — tone, texture, the slight unevenness of a lit sheet — and that detail costs file size to keep. A page scanned properly runs to hundreds of kilobytes or more. 41 KB is what's left once nearly all of that has been discarded: readable at a glance as too small, but only if you already know roughly what a scan is supposed to weigh. The number isn't dramatic. It's just quietly, precisely wrong for what the filename claims to be — a smaller, blunter version of what a name carrying five stacked endings tells you about a file that's been through more than its size lets on.

Who decided the file should be this small?

Nothing that asked first.

Somewhere between the scanner and whoever opened scan_0043.jpg, a step compressed it down — an email server enforcing a size limit, a messaging app squeezing attachments before it sends them, a storage system trimming what it keeps. None of those steps consult the sender. They apply the same rule to every file that passes through, and the rule doesn't know or care that this particular file was a document somebody needed legible. The 41 KB is a decision made on the file's behalf, after the fact, by whichever piece of the route it happened to travel through — the same kind of unasked decision that leaves a print stopping dead at an even white border on every side, made by a machine that was never going to ask permission first.

Why print something this small on a shirt?

Because the object it depicts was never meant to be looked at closely, and the print matches that.

Nobody frames a failed attachment. Nobody enlarges it. It exists at reading size in a file browser or an inbox and then gets deleted or ignored — a small, forgettable row among other rows. Printed small and left there rather than blown up to chest-filling size, it keeps that same proportion: something you'd walk up to and read, not something meant to announce itself from across a room.

Is there anything to license in an invented file listing?

No. scan_0043.jpg and 41 KB were written for this design and describe no real file.

A real attachment — an actual scan somebody actually sent, with its actual name and size — is a different case: it belongs to whoever made it, the way any document does, and reproducing that specific one is where clearing it is part of the job. A generic thumbnail icon, a generic numbered filename and an invented file size belong to nobody. Style has no owner. A work does.

Would this work with a different kind of file?

Most failed or truncated attachments carry the same three parts, and the specifics can shift without losing the point.

A photo that arrived as a broken box and 0 KB tells a starker version of it — nothing got through at all. It sits at the far end of the same shelf as a small picture stretched up to a size it was never recorded at: one file arrives too small to open, the other opens and turns out to have been too small all along. A document that shows a correct-looking size but still won't open tells a different one: the weight is right and the content still failed. What has to stay is the gap between what the filename promises and what the row actually delivers, since that gap is the entire joke.

Does it print well?

Yes — a crossed box, one line of type and one line of a number is about as little as a print can carry.

Two inks does it: a dark near-black for the box, the type and the hairline, and the dulled orange for the number alone, which keeps 41 KB reading as flagged without turning the whole row into a warning label. Nothing here needs to be large. At badge size on the chest, the thin diagonal in the box and the fine hairline rule are the only lines worth drawing slightly heavier than the screen version, so they hold in the weave. Sand, oatmeal or stone keep both inks legible without fighting the orange; a busier or darker ground starts to swallow a row this quiet.

How do I get one made?

Describe the file at JustOG — what the name should read, how small the number should be, and where on the chest the row should sit. Pick a direction, drag the crop frame, see it composited on the real garment, and it's made to order and shipped.

Designs other people have published are in the shop.

Whatever was in scan_0043.jpg is gone, and all that made it through is the receipt saying so.