All posts
August 14, 2026  ·  Updated October 2, 2026  ·  13 min read

UV DTF White and Varnish Layers Explained

Separate the artwork, white backing, clear ink and transfer-film responsibilities in a UV-DTF workflow. Use the equipment supplier’s file requirements and a controlled surface test.

UV-DTF white and varnish masks are two production separations with different jobs. White backs the colour so it remains visible on a dark, clear, or coloured object. Varnish controls clear ink above the colour. Neither plane is the adhesive. Build the masks from the intended finished stack, convert every pixel control to a physical distance, and verify layer order, polarity, mapping, mirror state, cure, and registration in the actual output queue.

Start with the finished decal, not the channel list

For a common reverse-transfer UV-DTF construction, read the functional stack from the object towards the viewer:

  1. Object surface: the cleaned, compatible substrate.
  2. Pressure-sensitive adhesive: supplied by the transfer-film system.
  3. White ink: an opaque backing under colour where required.
  4. Colour ink: the visible image.
  5. Clear varnish: the outer clear-ink region or selective finish.

Film A and film B move and protect that stack during printing, lamination, peeling, and application. They are not W or V planes in the artwork file.

Functional order is not automatically printer deposition order. A reverse-print queue may deposit varnish, then colour, then white against a carrier so that transfer presents the finished order above. Another device or film construction may require a different sequence. Record the exact printer, ink set, film pair, queue, mirror state, and documented layer sequence; do not infer them from filenames such as W1 and V1.

NestSheet’s current product prepares garment-DTF sheets from transparent PNG artwork and exports a CMYK + W1 TIFF for MainTOP or a transparent PNG for RIPs that build white. For a UV-DTF project, obtain the equipment and transfer-film supplier’s complete layer and file specification. The workflow planning page separates those preparation questions.

Give each plane one unambiguous job

PlaneSource intentGeometry ruleTypical file-side failure
ColourVisible RGB/CMYK artworkThe approved visible edgeWrong composite, conversion, scale, mirror, or crop
WhiteIntended opaque backingUsually inside or equal to the colour footprintMissing backing, an even white rim, weak edge support, or unintended white under faint alpha
VarnishIntended clear-ink coverageFull, selective, or intensity mask defined independently of whiteMissing highlights, a clear rim, unwanted flood, or flattened grayscale levels
AdhesiveA property of the film/application system, not an image planeDetermined by film construction and transferEdge lift or release failure that mask editing alone cannot solve

Do not clone one grayscale plane into the other merely because their silhouettes look similar. White answers “where does colour need opaque backing?” Varnish answers “where should clear ink exist, and at what encoded level?” A transparent hole may need neither; a white-only mark needs a real white source even though no coloured pixel can generate it; a selective gloss detail may need varnish beyond neither.

The spot-channel guide owns container structure, channel naming, polarity, and import semantics. Here the concern is how W and V geometry work together in the physical stack.

Define white from the intended finished appearance

Begin with the approved design and the object it will be applied to. Identify the colour areas that need opaque backing, intentional white-only artwork and transparent openings. Keep those choices visible in the artwork approval.

Use the equipment supplier’s documented process to prepare or generate the white separation. Record the source, physical size, chosen geometry and the receiving queue’s white controls. Inspect narrow lines, small text and isolated details alongside solid shapes.

A useful test keeps the artwork and material setup fixed while changing one white decision. Compare the received separation and the transferred sample, then record the observed result. Keep the approved white source with the colour artwork and queue settings.

Define the clear-ink finish separately

Specify which regions need clear ink and what the approved finish should look like. Obtain the expected mask representation, name, polarity and print sequence from the supplier for the exact printer and receiving queue.

Keep white and clear-ink responsibilities separate in the job record. White supports the intended colour appearance; clear ink defines the finish. Adhesion and release belong to the documented transfer-film and application process.

Use a sample containing full finish, a selective finish boundary and an intentional opening. Inspect the imported separation, then approve the transferred result on the actual surface. Record the film system, ink set, queue, handling and application steps used for that test.

Convert pixel controls to a physical allowance

A pixel value is incomplete until the output raster density is known:

millimetres per pixel = 25.4 ÷ output PPI
physical choke or spread = pixels × 25.4 ÷ output PPI
Output raster density1 px2 px
300 PPI0.0847 mm0.1693 mm
600 PPI0.0423 mm0.0847 mm
1200 PPI0.0212 mm0.0423 mm

Record geometry adjustments in both pixel units and physical distance, with the raster density used for the calculation. Select the adjustment through a controlled sample in the actual receiving workflow. NestSheet’s garment-DTF choke settings describe its own MainTOP production file; use the UV equipment supplier’s specification for the UV job.

Make the RIP prove the handoff

Obtain the required production file structure from the UV equipment supplier. Inspect each intended colour, white and clear-ink separation in the exact receiving queue. Confirm its coverage, physical size, orientation and assigned ink role before approving a transferred sample.

RIP-side checkPass conditionWhy it matters
Plane inventoryThe expected colour, W, and V planes appear once eachMissing or duplicated planes change the stack
Names and mappingEvery imported name maps to the intended device ink roleA label is not an ink assignment
PolaritySolid test regions show coverage; declared empty regions show noneByte conventions differ between separations and queues; NestSheet’s W1 uses 0 for full white and 255 for none
Dimensions and originColour, W, and V report the same canvas, scale, crop, and originCorrect masks can still be offset
Mirror and sequencePreview orientation and deposition order match the validated transfer constructionReverse transfer can invert intuitive visual order
Screening and ink limitsThe recorded queue settings match the approved testExtra passes or density changes cannot be inferred from channel count
Cure/exposureEvery layer uses the tested device-specific conditionA correct mask cannot compensate for under- or over-cure

Each W or V plane needs its own validated mapping in the receiving queue: the channel name identifies the plane, and the queue assigns the ink. NestSheet’s garment-DTF file carries one white plane named W1. Use the RIP handoff hub to record the exact environment, then compare the imported preview with known expected regions.

The queued PSD/PSB-versus-TIFF guide owns the container decision. Once a validated container is chosen, this layer check remains the same: inspect roles, coverage, alignment, sequence, and physical output.

Diagnose failures by their shape and interface

SymptomFirst branch to inspectWhat not to change first
White rim follows the entire colour perimeterAlpha edge, white threshold, physical choke, then bidirectional registrationVarnish density
White reveal is mostly on one sideColour-to-white registration, transport direction, shared origin, scale, mirrorA global alpha threshold
Clear rim extends past the intended finishV source, spread in physical units, V registrationWhite amount
Selective varnish is missing or floods the decalSource mask, gradient/binary choice, name, polarity, RIP mappingAdhesive or surface preparation
Colour loses opacity on a dark or clear objectWhite source, W coverage, polarity, mapping, ink limit, cureVarnish spread
Decal lifts cleanly from the objectSubstrate cleanliness, surface compatibility, adhesive film, application pressure, dwellW/V mask geometry
Ink stack separates internallyInk/film compatibility, layer sequence, inter-layer cure or exposureAlpha cleanup alone
Surface stays tacky, clouds, cracks, or abradesV load, cure/exposure, film handling, bend and material compatibilityChannel name alone

This ordering prevents a common category error: correcting a physical interface with an image operation. A mask edit is justified when the defect is already visible in that plane or follows its geometry. If source, exported planes, and RIP preview agree but the printed layers move or separate, continue in the device, material, and application branch.

Use a controlled three-mask proof

Before a production sheet, make a compact diagnostic file with:

  1. a solid colour shape with matching white and no varnish;
  2. the same shape with full varnish;
  3. a selective-varnish region with a hard boundary and, if supported by the validated queue, a declared grayscale ramp;
  4. an intentional transparent hole that must remain empty in W and V;
  5. a thin colour edge for measuring white choke;
  6. a varnish edge for measuring spread; and
  7. registration marks that let colour-to-white and colour-to-varnish displacement be measured in both axes.

Export the production file in the structure the UV equipment supplier specifies. Inspect colour, W, and V separately at 1:1; record output PPI, the white and clear-ink geometry settings, plane names, polarity, dimensions, mirror state, and checksum. Then import that exact file into the exact RIP/version/queue and print the smallest physically useful sample.

Approve each interface separately: object-to-adhesive, adhesive-to-ink stack, white-to-colour registration, and colour-to-varnish registration. The controlled DTF test-file protocol supplies the broader go/no-go record; this UV-DTF proof adds a distinct V mask and transfer-stack inspection.

Sources

Sources reviewed 2 October 2026. Confirm the exact layer order, file structure and process settings with the supplier for the equipment and film system used by the job.

Frequently asked

What is the functional UV-DTF layer order on the finished object?
For a common reverse-transfer stack, read from the object towards the viewer: substrate, pressure-sensitive adhesive, white, colour, then clear varnish. Film A and film B are transfer carriers, not ink separations. The printer may deposit the ink planes in the reverse visual order, so use the documented sequence for the exact film, printer, ink set, and queue.
How should I specify the white backing for a UV-DTF job?
Define the intended opaque backing with the artwork approval, then use the equipment supplier’s documented white-layer workflow for the exact printer and queue. Record the source, physical dimensions, coverage and any geometry adjustment. Inspect the received separation and approve a transferred sample on the intended surface before preparing the full order.
Is a varnish channel the same as the adhesive layer?
No. A varnish plane controls where clear ink is deposited. Transfer adhesion comes from the film-and-adhesive system, surface preparation, pressure, application, and material compatibility. Expanding a varnish mask cannot repair a contaminated substrate or incompatible adhesive.
How should I choose a varnish-mask representation?
Ask the equipment supplier which mask representation and ink mapping the selected queue expects. Record whether it uses a flat coverage region or controlled levels, then test known regions in the actual file. Inspect the received separation and a transferred sample before approving the finish for the intended object and material process.
How should I check white and clear-ink polarity?
Use a controlled file with regions whose intended ink coverage is known. Confirm the imported separation name, assigned ink role and displayed coverage in the exact receiving queue. Compare the result with a physical sample through the documented transfer process, then keep the file, queue and observation together in the production record.

Curious whether NestSheet handles your own orders better?