Artwork Files for a Team Store: What a Printer Actually Needs

The file that looks perfect in a presentation is often the file that prints badly. Not because anyone did anything careless, but because a screen is forgiving in exactly the ways a garment is not. A logo displayed two inches wide on a laptop can be the same file that has to hold up at fourteen inches across someone's chest.

The short answer: artwork needs enough resolution at its final printed size, a genuinely transparent background rather than a white one, and the original export rather than a copy that has been through a chat app. Most print problems are decided before anyone sends anything.

Resolution is a statement about size, not about the file

A file is not "high resolution" on its own. It is high resolution for a particular printed size, and the same file can be both at once.

The arithmetic is simple: pixels divided by inches gives you dots per inch. An image 3,000 pixels wide printed at 10 inches is 300 dpi. The same image printed at 15 inches is 200 dpi. Nothing about the file changed — only the size it was asked to cover.

This is why "it looks sharp on my screen" is not evidence. A screen shows perhaps a tenth of the detail a print demands, so a file can look flawless at viewing size and still be soft on a garment. Ask what size the design will print at, and check the pixel dimensions against it before sending.

Enlarging a small file does not add detail. Software can invent pixels, but it cannot invent information that was never captured — the result is a larger version of the same softness. If the artwork is too small, the fix is a new export from the original, not a resize.

A transparent background is not the same as a white one

This is the single most common file problem, and the most expensive to discover late.

Artwork for a garment normally needs the area around the design to be absent, not white. If the background is a solid colour, that colour is part of the image, and depending on the decoration method it can print as a filled rectangle around the design.

The trap is that the two look identical on screen. A white background against a white page is invisible. It only becomes obvious on a dark garment, at which point the item exists.

Two things make it checkable before then:

• Look at the file against a dark surface, not a white page. Most image viewers can show a checkerboard or a coloured backdrop behind transparency. If the area around the design stays white, it is not transparent.
• Check the file type. Formats differ in whether they can carry transparency at all. A format that cannot store it will never have it, whatever the design looked like when it was exported.

Whether a background must be transparent, and what happens if it is not, depends on the decoration method and the provider. Confirm it rather than assume — the decoration methods overview covers why the method changes the answer.

Send the original export, not a copy of a copy

Files degrade when they are re-saved, and the damage accumulates quietly.

Some image formats discard detail every time they are written in order to stay small. That is a sensible trade for a photo in an email and a poor one for artwork with hard edges and lettering, where the discarded detail shows up as fuzzy haloes and speckling around text.

The usual route to a damaged file is innocent: the design is exported once, then sent through a messaging app that compresses it, then downloaded, then re-sent. Each step is reasonable. The file that arrives is several generations from the original.

Ask for the export from whoever created the design, transferred in a way that does not recompress it. If the only copy available has been round-tripped, that is worth knowing early, because it cannot be repaired afterwards — the detail is gone, not hidden.

Keep the source, not just the export

The export is a flattened picture. The source is the editable document it came from.

With the source, a design can be re-exported at any size, with or without a background, in whatever format is needed next season. Without it, every future request is limited by whatever the one surviving picture happens to contain.

Store the source somewhere that outlasts the person who made it, and note what it was made in. This matters more than it sounds: designs are often created by a parent, a student, or a volunteer, and the file lives on their device until it does not.

A short checklist before sending

• What size will this print at, and how many pixels wide is the file?
• Is the background transparent, checked against a dark backdrop rather than assumed?
• Is this the original export, or a copy that has been through other apps?
• Do we have the editable source, and does someone other than its author have a copy?
• Are the colours specified somewhere, rather than only visible in the picture?

None of these require design skill. They require asking before the order rather than after it.

Frequently asked questions

How do I know if my logo is big enough? Divide the pixel width by the printed width in inches to get dots per inch, and compare that against what the provider asks for. The same file can be sufficient at one size and insufficient at a larger one.

Can a small logo be enlarged? It can be made larger, but enlarging does not add detail that was never in the file. The result is a bigger version of the same softness. A new export from the original source is the only real fix.

Why does my artwork have a white box around it on a dark garment? Usually because the background is solid white rather than transparent, which is invisible against a white screen. Viewing the file against a dark backdrop reveals it before the garment does.

Does it matter how I send the file? It can. Some apps recompress images automatically, and formats that discard detail lose a little more each time they are saved. Send the original export by a route that transfers it unchanged.

What should we keep after the season? The editable source file, not only the exported picture, along with a note of what it was created in and who holds a copy.