DTF File Requirements: What Customers Should Upload

A customer uploads a logo, pays for a gang sheet, and the transfer comes out of the printer looking soft, with a faint white rectangle hugging the design. The file was a 400 pixel JPG saved from a website. Nobody did anything wrong on purpose, but you just ate a reprint. Clear DTF file requirements, posted where customers can see them and enforced at upload, stop most of these problems before money changes hands.

This guide covers what a DTF file needs to be (format, resolution, transparency and sizing), the file types that cause the most trouble, and how a gang sheet builder like Buildaur checks uploads automatically. It ends with a plain-language requirements page you can copy and hand to customers.

The short answer: transparent PNG at 300 DPI, sized to print

The one-line version: a PNG with a transparent background, at 300 DPI at the size it will print, no wider than your sheet. The rest of this article explains why those rules exist and how people break them. Here is the full checklist:

• Format: PNG with an alpha channel (transparent background). Vector files such as SVG or PDF are also great when your tool can rasterize them cleanly.
• Resolution: 300 DPI at print size. A 10 inch wide design needs roughly 3000 pixels across, regardless of what the file's metadata says.
• Color: sRGB is fine for nearly every DTF workflow. The RIP handles conversion to the printer's inks, including the white underbase.
• Orientation: upload art reading correctly, not mirrored. The RIP flips the sheet for the film.
• Transparency: anything that should not print must be fully transparent. Anything that should print white must be actual white pixels.
• Clean edges: no stray pixels, no leftover checkerboard, no pale fringe from a sloppy background removal.
• Sizing: the art is no wider than the sheet, with a little breathing room between designs.

Why resolution matters more than file size

Customers often equate a big file with a good file. In DTF the only number that matters is pixels at the final print size. A 300 KB PNG exported from a vector logo at 3600 by 1200 pixels prints crisp at 12 inches wide. A 20 MB photo cropped down to a small logo may still be blurry at 8 inches.

Use these pixel counts as your reference for 300 DPI:

• 3 inches wide: at least 900 pixels
• 4 inches wide: at least 1200 pixels
• 8 inches wide: at least 2400 pixels
• 11 inches wide: at least 3300 pixels
• 12 inches wide: at least 3600 pixels
• 22 inches wide: at least 6600 pixels

The "300 DPI" value stored inside a file is just a label. A 600 by 600 pixel file can carry a 300 DPI tag while still printing as a soft 2 inch square. That is why a good upload tool compares actual pixel dimensions to the size the customer chose, and why a DTF 300 DPI rule should always be stated as "at print size."

What about upscaling?

Upscale and enhance tools are genuinely useful for art that is a little short, say 220 DPI at print size. They cannot invent detail that was never captured, so a 300 pixel avatar blown up to a full back print still looks like a 300 pixel avatar with smoother blur.

Gang sheet file size in practice

The finished gang sheet is another story. A 22 by 60 inch sheet at 300 DPI is 6600 by 18000 pixels, and the PNG your RIP receives can run to hundreds of megabytes. That is normal for shop output. Customer uploads should be sized to their print dimensions and typically land under a few tens of megabytes each.

Transparent backgrounds and the white-box problem

DTF printers lay down white ink under every opaque pixel so colors stay bright on dark garments. That is also why a white background that looks invisible on a white web page prints as a solid white rectangle around the logo. The printer cannot tell "background white" from "design white."

A transparent PNG for DTF solves this because transparent pixels get no ink at all. The most common ways customers lose that transparency are:

• Saving as JPG, which flattens everything onto a solid background.
• Taking a screenshot of a transparent image, which bakes the gray and white checkerboard into the file.
• Exporting from a design tool with "transparent background" unchecked.

The reverse problem: white that should print

The mistake also runs the other way. White text or outlines intended for a black hoodie must be real white pixels. Some designers knock out white to transparent so a mockup looks right on a white canvas, and the finished transfer arrives with the white parts missing. Always preview art on a dark background, because that is where both errors become obvious.

Automatic background removal

Background removal built into the builder handles the everyday case well: a logo or text on a solid color background. It struggles with hair, drop shadows, pale subjects on light backgrounds and soft edges. Encourage customers to zoom in and check the edges before paying, or offer cleanup as a paid add-on.

Stray pixels, halos and thin lines

These three issues are invisible on a phone screen and obvious on a shirt.

Stray pixels

A rough background removal often leaves single pixels or tiny clusters floating around the art. Each one gets white ink, color ink and adhesive powder, then cures into a hard little dot on the garment. A dark preview background and a scan at 100 percent zoom catch most of them, and a knockout or eraser tool removes them.

Halos

When a design with dark edges is removed from a white background, the anti-aliased edge pixels that blended into the white stay behind as a pale fringe. Printed, it reads as a faint light ring around the design. Tighten the selection by a pixel or two, or remove the background from the original layered file instead of a flattened export.

Thin lines and tiny text

DTF holds detail well, but there are limits. Hairline strokes and letter strokes under roughly 1 point tend to break up, either at the print stage or when the film is peeled. Keep line weights and letter strokes at about 1 point or heavier, and treat anything thinner as a risk worth flagging to the customer.

Sizing art for the sheet width you sell

Most shops sell a fixed sheet width, often around 22 inches for DTF and narrower for UV DTF, with the length priced by the inch. The width of a customer's design is therefore a hard constraint and the length is flexible. Three sizing habits save back and forth:

1. Decide the print size first. A left-chest logo is usually 3 to 4 inches wide, a standard front graphic 10 to 12 inches, a full back 12 to 14 inches. Customers who know their target size can check pixel counts before uploading.
2. Leave a gap between designs. A quarter to half inch of space makes cutting fast and keeps neighboring transfers from sticking together. The auto-nesting packer in a builder handles this for you.
3. Rotate wide art. A 16 inch banner fits fine on a 22 inch sheet turned sideways. Build the hint into your requirements page or let the packer do it.

UV DTF sheets are typically narrower and the transfers are applied to hard goods rather than fabric, which changes what "too small" means. If you sell both, the UV DTF vs DTF comparison covers how the file rules diverge.

Files that cause trouble: JPGs, screenshots, low-res logos

Here is how the common upload types compare for DTF work.

JPGs

JPG is the number one cause of the white-box reprint. Even when the background is meant to print, JPG compression adds blocky noise around edges and text that shows once white ink is laid under it. Ask for PNG every time.

Screenshots

Screenshots capture whatever was on screen at screen resolution, far below print resolution, often with a baked-in checkerboard or a slice of the interface. When a customer says "I only have a screenshot," the original usually exists somewhere and is worth finding.

Low-res logos

Small business customers often have one copy of their logo, pulled from a website header or social profile. It is 500 pixels wide, perfect for a left chest and useless as a full front print. Explain the pixel math once, kindly, and many will go back to their designer for the vector file.

How a builder enforces DTF file requirements automatically

A written requirements page helps, but most customers do not read it. The reliable fix is an upload flow that checks the file for them, which is a core part of what a gang sheet builder does. At upload, a good builder will:

• Accept PNG (and optionally vector formats) and reject or warn about anything else.
• Read the actual pixel dimensions and compare them to the size the customer selects, then show a low-resolution warning when the math falls short of 300 DPI.
• Offer one-click background removal, plus tools to recolor, replace a color, knock out an area, upscale or add halftone effects.
• Flag art that runs off the sheet edge or overlaps a neighboring design so nothing gets clipped or double-printed.
• Preview against a dark background so stray white pixels and missing white are visible before checkout.
• Render the final sheet as a high-resolution PNG at 300 DPI, so your RIP gets a consistent file every time regardless of what was uploaded.

Buildaur's builder runs the resolution, off-sheet and overlap checks as the customer works, includes the background removal and image tools above, and the shop downloads press-ready print files from the orders dashboard. You can see how the output side works at the output section of the platform overview. For the broader playbook on catching bad uploads early, see how to reduce DTF reprints from bad uploads.

Automated checks cannot judge whether a halo looks bad or whether a white area was meant to be transparent, so keep a human glance on anything that trips a warning.

A file requirements page you can share with customers

Post this on your storefront, link it from your order confirmation email, and paste it into chat when asked. Edit the sheet width to match what you sell.

Artwork requirements for DTF transfers

1. Upload a PNG with a transparent background. No JPGs, no screenshots, no photos of your design on a shirt.
2. Your file should be 300 DPI at the size you want it printed. Quick check: multiply your print width in inches by 300. A 10 inch design needs at least 3000 pixels across.
3. Anything that should be blank on the shirt must be transparent, not white. Anything that should print white must be white in the file.
4. Check the edges. Zoom in and look for leftover dots, gray fringe or bits of background. Remove them before uploading.
5. Keep lines and small text at least 1 point thick. Very fine detail may not survive the transfer.
6. Upload art the right way around. Do not mirror it; the shop mirrors the sheet for printing.
7. Designs can be up to 22 inches wide. Wider art will be scaled down or rotated to fit.
8. If you only have a low-quality copy of your logo, ask your designer for the original vector file (AI, EPS, SVG or PDF).
9. Not sure? Upload it anyway. The builder warns you if the resolution is too low, and you can message us before you pay.

A note on tone. Customers respond better to "here is how to get a great print" than to "we are not responsible for bad files." State the rules, give the one-line reason behind each, and make it easy to ask for help. You will still see the occasional 400 pixel JPG, but far fewer, and with a warning attached instead of a reprint.

Where Buildaur fits

Buildaur is gang sheet builder software for DTF and UV DTF shops that builds these requirements into the upload flow: low-resolution, off-sheet and overlap warnings, background removal and image tools, and 300 DPI PNG print files ready for your RIP. It runs on a flat monthly fee, never a percentage of your sales, with a 7-day free trial. Current pricing is at /platform#pricing.

If you would rather have the builder catch bad files than catch them yourself, start your free trial and have a branded builder live in about a minute.