A print-ready DTF file has a known final size, enough real source pixels for that size, intentional transparency, and a colour path the shop has tested. For ordinary colour artwork, a clean transparent PNG is a practical intake file. Use a verified spot-bearing TIFF or PSD/PSB workflow when separate white or varnish planes must survive the handoff. Container choice never replaces preflight.
The minimum viable intake specification
Give customers and operators requirements they can test, not a list of slogans. A minimum viable intake file should meet all of these conditions:
- Final size is explicit. Record width and height in one physical unit, plus any allowed rotation.
- Pixel dimensions support that size. Calculate effective artwork PPI from the actual pixels and intended inches.
- Transparency is intentional. Outside pixels are fully transparent; shadows, distress and soft fades are reviewed rather than deleted automatically.
- Artwork is complete. Fonts and linked assets are not missing; rasterized output is visually compared with the approved design.
- Colour expectations are stated. The source colour space and any proof/reference are supplied; an embedded profile is not assumed to control every later conversion.
- Production planes are identified. If the customer supplies white or varnish separately, document the plane names, polarity and expected mapping.
- A production export has been reopened. Size, alpha, colour, bounds and separations are checked in the file that will actually move downstream.
NestSheet’s current visible intake hint emphasizes PNG, TIFF, PSD and PSB and asks for 300 PPI as a practical target. A universal technical ceiling protects the upload and processing pipeline; it does not vary by plan. Treat the PPI figure as an intake target—not printer DPI, a quality guarantee or a universal rejection threshold. The application’s resolution checks are advisory, and usable source resolution depends on artwork content, print size and the shop’s test standard.
Choose a container for the job
“Accepted” and “recommended” are different. The current NestSheet server route recognises ten input container families: PNG, JPEG, TIFF, WebP, PSD, PSB, EPS, AI, PDF and SVG. Some have two filename extensions, such as JPG/JPEG and TIF/TIFF. The browser’s primary drag/drop path and the separate DTF preflight rules do not expose that whole set identically, so production guidance should lead with the formats actually validated in your intake path.
| Container | What it is useful for | Transparency or spots | Production caution |
|---|---|---|---|
| PNG | Straightforward colour artwork with clean edges or alpha | RGBA transparency; no named white/varnish spot planes | A checkerboard can hide low-alpha residue; confirm final size and alpha |
| JPEG | Opaque photographic colour when transparency is unnecessary | No alpha and no named production spots | Compression and an automatically opaque background make it a poor default for cut-out art |
| TIFF | High-fidelity raster intake and verified separated production handoff | May carry alpha or additional ink planes depending on structure | “TIFF” alone does not prove the RIP will map its channels correctly |
| PSD / PSB | Large or complex raster source and certain spot-bearing handoffs | Can represent extra channels; PSB handles larger documents | NestSheet’s current export is flattened with extra spot channels, not a promise to preserve editable source layers |
| WebP | Compact colour/alpha intake accepted by the canonical path | Can carry alpha; no NestSheet spot-bearing output contract | It is not in the primary production hint; test the exact browser intake before standardising on it |
| EPS / AI / SVG | Vector-origin artwork that needs rasterisation for this workflow | Named vector structures are not guaranteed to survive as production spots | Inspect rasterised edges, dimensions and colour; old or unusual constructs can behave differently |
| Page-based artwork intake | Structure varies; current canonical intake uses the first page | Confirm page choice, crop, transparency and rasterisation; do not infer PDF/X or spot preservation |
Every accepted upload is normalised to a canonical RGBA working image for downstream placement and Prep; the original upload is retained separately. That normalization boundary is why “the source opened” is not enough. Inspect the canonical result before production.
For output, the current Studio exposes TIFF, PNG, flattened PSD and flattened raster PDF. Those outputs do not all preserve the same information. PNG is the simple colour-plus-alpha lane; TIFF and PSD are the relevant lanes when separate production spots are needed; the current raster PDF lane has no white or varnish spot planes. See TIFF versus PNG for DTF gang sheets and the current export matrix before choosing the handoff.
Calculate effective PPI at final size
Artwork resolution is physical. The useful calculation is:
physical width in inches = pixel width ÷ effective PPI
effective PPI = pixel width ÷ intended width in inchesA 1,800-pixel-wide design placed at 6 inches is 300 PPI. The same source placed at 12 inches is 150 PPI. Its metadata can say 300 in both cases; placement size determines the effective value. For metric production, convert millimetres to inches by dividing by 25.4 before calculating.
This is image PPI, meaning source pixels per printed inch. A printer’s DPI describes how the device addresses dots or drops and belongs to the downstream output configuration. Writing “300 DPI” into an image field does not set printer behavior.
Resampling is also distinct from changing resolution metadata. With resampling off, changing the PPI value changes the calculated physical size but leaves the pixel grid intact. With resampling on, software adds or removes pixels. An interpolation method can make enlargement look smoother, but it cannot reconstruct fine type, texture or edge information absent from the source. Inspect at final print size and request a better original when the missing detail matters.
NestSheet’s current Studio calculates effective resolution from source pixels at placed physical dimensions. Its warnings remain advisory; they do not make every low-reading image unusable or every high-reading image good. A hard-edged logo, a noisy photograph and tiny text can fail differently at the same number. Put your acceptance threshold in a shop-controlled test standard rather than presenting one PPI value as physics.
Inspect transparency, not just the checkerboard
PNG alpha is a per-pixel opacity signal. It is valuable because prepress can use it to define visible colour and derive an initial white mask, but the signal may contain more than “art” and “no art.”
| Pixel condition | What the colour preview may show | DTF risk |
|---|---|---|
| Alpha 0, no visible pixel | Empty background | Usually outside the printed shape, although hidden RGB can resurface after later alpha operations |
| Very low nonzero alpha | Apparently empty checkerboard | Can create dust, haze, an oversized bound or unexpected white-mask pixels |
| Intentional soft alpha | Shadow, feather, smoke, distress or anti-aliased edge | A hard cleanup can damage the design; underbase thresholding changes its appearance |
| Alpha 255 | Fully opaque colour | Straightforward input to alpha-derived white, subject to the chosen choke and amount |
| Opaque background | White or coloured rectangle around art | The rectangle is part of the image and may receive white unless removed |
| Transparent padding | Nothing visible around the art | Inflates rectangular bounds and wastes placement space even if it does not print |
Reopen the exported PNG over a dark background, a light background and a high-contrast coloured background. Zoom into the edge and inspect the white-channel preview. The official checkerboard is a viewing aid, not a preflight result. Files created in Canva deserve the same test; the transparent-PNG cleanup guide covers that specific path.
NestSheet preserves native PNG alpha during canonical normalization; an opaque PNG receives a synthetic fully opaque alpha channel. JPEG also becomes opaque. That behavior is predictable, but it cannot infer that a white rectangle was supposed to be transparent.
Treat colour space and ICC handling as a workflow
There is no context-free answer to “RGB or CMYK for DTF.” The correct question is: which source interpretation, conversion and RIP output path has this shop validated?
RGB is a practical interchange path for transparent artwork and keeps alpha handling simple. It does not mean every bright screen colour is printable. CMYK may be appropriate when the creator and shop share a controlled source profile and proofing process. It does not mean four supplied values pass unchanged through normalization, RIP conversion, ink limiting and the printer.
An ICC profile describes how numeric colour values relate to a colour space or device condition. Embedding one can preserve source intent only when the receiving application reads and uses it as expected. Detection is not the same as conversion, and conversion is not the same as preserving the profile in a new file. The DTF ICC profile guide explains the upstream-versus-RIP boundary.
NestSheet detects source colour-space and profile metadata and normalizes supported uploads to a canonical RGBA working image. The main separated CMYK TIFF and PSD paths currently convert toward sRGB using NestSheet’s bundled CMYK source profile when those assets are available; they do not promise to honour or preserve an arbitrary embedded input ICC. If that distinction matters to a calibrated job, convert through the shop’s approved colour workflow before upload and compare a known reference. NestSheet also does not currently promise a customer-uploaded custom output ICC in Studio; select only an output option that exists in the current export workflow and validate the result downstream.
This is deliberately narrower than saying “embedded profiles are respected.” The file may retain useful metadata for reporting while the working pixels follow a defined normalization path. Judge the pixel result and RIP proof, not the presence of an ICC label alone.
Preflight before nesting or export
Use this operator checklist on the canonical working image and again on the final production export:
- Identity: filename, order, artwork version and copy count match the approved job.
- Size: intended width and height are recorded in inches or millimetres; no silent fit-to-page scaling is planned.
- Pixels: effective PPI is calculated at that size; fine details are inspected rather than judged by metadata.
- Bounds: transparent padding is trimmed where safe; no artwork falls outside the sheet.
- Alpha: opaque backgrounds, low-alpha debris and intentional fades are distinguished.
- Colour: source space, reference and conversion responsibility are known; embedded metadata is not treated as proof of handling.
- White: alpha-derived versus file-supplied source is chosen deliberately; threshold, choke and amount are previewed.
- Spots: channel count, names and polarity match the tested handoff; PNG is not mistaken for a spot-bearing file.
- Output: exported pixels, physical size, mirror state and separations are checked in the target RIP/version.
- Test: unfamiliar artwork, conversion or queue changes receive a controlled print before a full run.
NestSheet can surface missing-transparency, overlap, off-sheet and effective-resolution issues, but current Studio preflight is advisory. Export responsibility remains with the operator. Use the product workflow for Prep and packing, then make the RIP preview part of release—not an afterthought.
Sources
- Adobe, Set image size and resolution: https://helpx.adobe.com/photoshop/desktop/crop-resize-transform/resize-adjust-resolution/set-image-size-and-resolution.html
Adobe documentation checked July 2026. NestSheet format, normalization and export statements were verified against the shipped repository on 21 July 2026; target-RIP acceptance and shop quality thresholds still require local validation.
