Keep the editable artwork master in the source editor and use a defined production file for the receiving queue. In NestSheet’s Production DTF preset workflow, the input is an approved transparent PNG and the output is a mirrored 300 dpi CMYK + W1 TIFF for MainTOP. Photoshop documents and TIFF handoffs serve different roles in that source-to-print record.
Make a handoff decision, not a quality ranking
PSD/PSB and TIFF can carry a colour image plus production spot planes, but they solve different operational problems.
- A Photoshop-readable checkpoint lets a person inspect the composite and Channels panel, compare names and polarity, and—after a validated round trip—make a controlled channel edit.
- A direct-to-RIP file avoids that editor step. The exported artefact moves unchanged into the validated queue.
Neither path is automatically more accurate. The correct path is the shortest one that preserves every required plane and has a receipt in the exact downstream environment.
The underlying channel concepts—colour, alpha, generated white, serialized white, varnish, names, and polarity—belong in DTF spot channels explained. This comparison starts after those planes have been chosen.
Define the two files you need to retain
An editable master supports artwork changes and approval. A production file records the exact raster and white separation passed to the receiving queue. Keep each file’s purpose clear when preparing repeat work.
| Record | Role | Operator check |
|---|---|---|
| Photoshop master | Editable artwork and design history | Correct revision and approval |
| Transparent PNG | Artwork supplied to NestSheet | Pixel detail, alpha and intended print size |
| Production TIFF | Sheet exported for MainTOP | CMYK + W1, 300 dpi, mirrored and chosen choke |
| Job record | Connects the source to production | Quantities, dimensions, queue and sample result |
This comparison describes the current NestSheet handoff checked on 2 October 2026. Use the actual source editor and receiving queue documentation for any different file workflow.
Compare the handoff responsibilities
| Decision | Artwork master | Current NestSheet production TIFF |
|---|---|---|
| Purpose | Make and approve source-design changes | Supply a prepared gang sheet to MainTOP |
| Physical size | Record the intended dimensions with the design | Check sheet dimensions in the receiving queue |
| Transparency | Export the approved edge as PNG alpha | White is carried separately as W1 |
| White decision | Keep any source intent in the artwork approval | Sheet-wide choke of 0, 1 or 2 px |
| Repeat work | Retain the editable source revision | Retain the exact approved downloaded TIFF |
After an artwork change, export a new PNG and review its placed dimensions and copies. After a layout or choke change, create a clearly identified production TIFF and inspect it in the receiving queue. This keeps each revision connected to the decision that created it.
What NestSheet currently writes
NestSheet accepts transparent PNG artwork and prepares gang sheets with Auto-nest or Manual placement. Set print sizes, copies, roll width, gap and margin, then choose a sheet-wide choke of 0, 1 or 2 px. The Production DTF preset writes a mirrored 300 dpi TIFF with CMYK and one W1 white channel for MainTOP.
The export dialog shows the production format, colour, white, channel count, resolution and transfer orientation together. Check the selected choke and choose a useful filename before exporting.
Use the canvas to inspect artwork coverage, then inspect the exported W1 for the final white edge and fine details. Open the file in MainTOP and confirm dimensions, orientation and white mapping. Keep the result with the source revision used to prepare the sheet.
What “editable handoff” means
Adobe documents spot channels as separate production information and tells Photoshop users to save spot channels in PSD or TIFF. It also warns, in effect, that the name must be recognised by the receiving application. Grayscale values in a spot channel represent spot density; the display colour and Solidity setting affect the on-screen composite preview rather than the separation itself.
Within that model, “editable” can safely mean:
- inspect the flattened colour composite;
- show each production spot separately;
- compare a spot against known white/no-white test regions;
- rename a channel when the downstream contract requires another label; and
- edit a raster spot mask, if that edit is controlled and independently checked.
It cannot mean that text remains live, logos remain vector, customer designs can be rearranged as separate objects, or the original authoring document can be recovered. Call the file a flattened composite plus production channels, not a layered design master.
An editor round trip is also a transformation, not a neutral viewing action. Before making it part of production, open and save a small fixture, then compare pixel dimensions, physical density, colour mode, ICC presence, spot count, names, polarity, and selected sample regions. A changed overall file hash is not by itself a failure—metadata and encoding can change—but the production semantics must not.
Keep container limits separate from compatibility
Adobe’s current file-format specification defines PSD as version 1 with a maximum of 30,000 pixels in either dimension and PSB as version 2 with a maximum of 300,000. Use those format limits when preparing a Photoshop document in the source editor. For NestSheet, export approved transparent PNG artwork and use the Production DTF TIFF handoff.
The current NestSheet production TIFF uses the classic TIFF container. LibTIFF documents the normal 4 GB ClassicTIFF boundary and BigTIFF’s 64-bit offsets. Moving to BigTIFF would address an offset boundary, not the target application’s support, decoded memory, dimension limit, or channel mapping. This article therefore does not recommend BigTIFF as a compatibility escape hatch.
Container, channel representation, editability, size boundary, and target acceptance are five separate columns. A workflow can pass four and fail the fifth.
Approve the receiving file workflow
The current NestSheet production preset targets MainTOP. Open the actual exported TIFF in the queue used for the job and inspect physical dimensions, orientation, CMYK colour and W1 white coverage.
For another proposed handoff, obtain the supplier’s expected file structure and test it in the exact edition, driver and queue. Keep the sample file and result with the production record. The RIP workflow guides provide a checklist for gathering those requirements.
Test the two candidates with the same job
Use one small diagnostic job, not two convenient examples. Keep physical size, PPI, bit depth, colour mode, white/varnish count, names, ICC choice, and intended queue constant. Include obvious colour-backed white, no-white, and white-only regions so polarity errors cannot hide in a thumbnail.
| Checkpoint | PSD/PSB candidate | TIFF candidate | Record as pass only when… |
|---|---|---|---|
| Independent open | Open in a current Photoshop-compatible reader | Open in a reader that exposes the exact TIFF planes | Container, dimensions, colour mode, and channel count are reported as expected |
| Composite | Compare against the approved flattened colour reference | Compare against the same reference | No spot mask appears as visible grey colour and no colour region disappears |
| Spots | Inspect every W/V channel separately | Inspect every W/V extra plane separately | Count, order, names, polarity, and diagnostic regions match the declared contract |
| Metadata | Inspect physical density and ICC presence | Inspect the same fields | Intended physical size is unchanged and the chosen profile is present as expected |
| Editor round trip | Open, save a copy, and repeat every check | Do this only if TIFF editing is part of the real workflow | Composite and production semantics survive; do not rely on “it saved” |
| RIP import | Import into the exact product/version/queue | Import into the same queue | Size, composite, plane discovery, device mapping, polarity, and colour-to-spot registration are all explicitly checked |
| Physical test | Print the same small target | Print the same small target | The shop records the equipment/material stack and its own observed result |
The visual method in reading your RIP’s white-channel preview can help inspect coverage, but a clean preview cannot guarantee ink delivery, powder, cure, press, or wash behaviour. Those remain physical evidence.
Rename spots at the controlled boundary
NestSheet’s Production DTF preset names its white separation W1. Record that file specification with the receiving MainTOP queue. If another workflow requires changes to a production file, make the edit at a documented step and repeat the receiving-file and sample checks for the revised result.
Rename after export only when all three statements are true:
- the target contract requires another name;
- the chosen editor is part of the documented workflow; and
- its open/save round trip has passed the comparison above.
Renaming is not mapping. A channel named White, W, or W1 remains raster data until the target queue assigns it to the intended device role with the correct polarity. Conversely, changing a label does not repair wrong mask bytes. Verify the image and the mapping separately.
A practical decision sequence
- Decide who owns white. If the validated RIP derives white from clean transparency, use that lane; do not add prebuilt spots merely because another format can carry them.
- Declare the production planes. If the file must carry W/V, record count, names, polarity, colour mode, bit depth, PPI, and physical dimensions.
- Prefer the proven direct path. If the exact queue has a current controlled receipt for the NestSheet production TIFF, send that unchanged TIFF.
- Add a Photoshop checkpoint for a reason. Choose PSD/PSB when a person must inspect or deliberately edit the composite/spots, then validate the editor round trip and RIP import.
- Respect the container boundary. Above 30,000 pixels in either dimension, PSD becomes PSB. Proceed only if every downstream application in the chain accepts the tested PSB.
- Treat unknown as unknown. If neither candidate has current evidence, run the small comparison. Do not turn a vendor name, familiar extension, or successful thumbnail into an acceptance claim.
- Release only after the physical control. The winning file is the one whose complete digital handoff and small production test pass in the shop’s recorded environment.
The result may be TIFF for one queue and PSD/PSB for another. It may also be RGB+alpha when the downstream workflow builds white. That is not inconsistency; it is a documented handoff boundary.
Sources
- Adobe, Print spot colors — spot channels, names, density, and PSD/TIFF preservation guidance.
- Adobe, Photoshop File Formats Specification — PSD/PSB structure, versions, dimensions, and channels.
- Adobe, Save files in graphics formats — TIFF options and application-interoperability boundary.
- LibTIFF project, BigTIFF Design — ClassicTIFF offsets and the 64-bit BigTIFF extension.
- CADlink Digital Factory, Transparency Opacity Tool and Jobs menu output tools — examples of downstream transparency/underbase and device-spot concepts, not proof of PSD/PSB/TIFF acceptance.
