Skip to content
Cut & StackA PDFIMPOSE FIELD GUIDE
The workflowField notesQuestions
Open PDFImpose
Cut & Stack / FIELD NOTES
Guide

Double-Sided Cut and Stack: Keeping Fronts and Backs Paired

In double-sided cut and stack, every back must land directly behind its own front, so the back grid is a mirror of the front grid. A sideways (long-edge on a portrait sheet) turn mirrors the columns; a head-over-foot (short-edge) turn mirrors the rows. Work out the block arithmetic in items, not PDF pages, keep numbering on one side where you can, mirror stubs and offsets with the grid, and prove the pairing with a short marked test stack before the run.
Neatly cut ticket stacks beside a printed ticket sheet and trimming tools.
Workflow illustrationCut & Stack

What changes when a cut and stack job prints on both sides?

Single-sided cut and stack has one ordering problem: the sequence has to run down each pile. A double-sided job adds a second, independent problem: the back printed behind each position has to belong to the item on the front of that position. The two problems fail in different ways. A pile-order fault shows up as numbers that jump at a pile boundary. A pairing fault shows up as a ticket whose back belongs to a different ticket, or a flashcard whose answer belongs to another question, and it can look perfectly tidy until someone reads both sides.

The cause is physical. When a sheet is turned over, the position that was on the left of the front is now on the right of the back, or the top row has moved to the bottom. The imposed back page therefore cannot use the same grid order as the front. It has to be mirrored across the axis the sheet turns on.

How does the block arithmetic work for duplex items?

Count items, not PDF pages. A duplex source file usually alternates front and back, so 1,000 tickets arrive as 2,000 pages: front of 1, back of 1, front of 2, and so on. The block calculation uses the 1,000 items.

  • Positions per side: 4 (a 2 by 2 grid).
  • Block size: 1,000 ÷ 4 = 250 items per pile.
  • Sheets: 250, each printed on both sides, so 500 printed sides.
  • Sheet k, position p carries item 250 × (p − 1) + k on the front, and the back of that same item behind it.

The common mistake is to feed the 2,000-page count into a single-sided calculation. That produces blocks of 500 and treats backs as separate items, so fronts and backs end up in different piles. If your tool expects separate front and back files rather than an interleaved one, check that both contain the same number of pages in the same order before imposing.

Which way is the back grid mirrored?

It depends on the axis the sheet turns on, not on the words in the printer driver. Take a portrait sheet with four positions: A top-left, B top-right, C bottom-left, D bottom-right. On the first sheet of the 1,000-ticket job, A carries ticket 1, B carries 251, C carries 501 and D carries 751. Viewing each side face up on screen, the backs must sit like this:

Back position (as viewed on screen)Sideways turn: long-edge flip on a portrait sheet (head to head)Head-over-foot turn: short-edge flip on a portrait sheet (head to foot)
Top-leftBack of 251Back of 501
Top-rightBack of 1Back of 751
Bottom-leftBack of 751Back of 1
Bottom-rightBack of 501Back of 251

A sideways turn swaps columns and keeps rows; a head-over-foot turn swaps rows and keeps columns. On a landscape sheet the labels trade places, because the long edge is then the top and bottom edge, which is why "long edge" on its own is not a reliable instruction. Press work uses the same distinction: work and turn flips the sheet side to side and keeps the gripper edge, while work and tumble flips it head over foot and moves the gripper to the former tail.

Head to head and head to foot describe how the finished piece reads. With head to head, a ticket turned sideways shows an upright back. With head to foot, it has to be turned top over bottom, like a wall calendar. Agree which one the customer expects before choosing the flip, because the imposition then follows from that choice.

Front grid and mirrored back grid for a sideways turn The front sheet shows tickets 1 and 251 on the top row and 501 and 751 on the bottom row. The back sheet, viewed face up after a sideways turn, shows the backs of 251 and 1 on the top row and 751 and 501 on the bottom row. Front 1 251 501 751 Back, sideways turn B251 B1 B751 B501
Sheet 1 of a 1,000-ticket, 4-up duplex job. The back columns swap so each back lands behind its own front once the sheet is turned.

Should the numbers go on one side only?

Where the design allows it, yes. If the front carries the number and every back is the same static artwork (terms, a sponsor panel, a map), a pairing fault cannot put the wrong back on a ticket, because every back is identical. The mirroring still matters for geometry, since an asymmetric back such as a panel that must sit over the stub has to land in the right place, but the content risk disappears.

The risk returns whenever the back is variable: a repeated number for a security check, a different answer on each flashcard, a name on the reverse of a badge. Treat those jobs as two linked data streams and check pairing on every proof, not just pile order. Generate the numbers on the flat file before imposing, as described in the numbered tickets workflow, so the front and back of each item share one record and cannot drift apart. The sibling guide on numbered raffle tickets covers prefixes and leading zeros for that step.

How do stubs, gutters and offsets line up on the back?

Anything that is not symmetrical about the turn axis has to be mirrored with the grid, not copied.

  • Stubs. A stub on the left of the front ticket is on the right when that ticket is viewed from the back after a sideways turn. If the back has text that must stay off the stub, its stub zone belongs on the right of each back position.
  • Perforations. A perforation goes through both sides at once, so it must fall in the same physical place on front and back. Keep back artwork that crosses the perforation line deliberate, not accidental.
  • Off-centre grids. If the grid is pushed toward one edge, for example to leave a wider gripper margin, the back grid must be pushed toward the mirrored edge. A sideways turn keeps the gripper edge, so only left and right offsets mirror. A head-over-foot turn moves the gripper to the opposite end, so the head and tail margins need planning on both sides.
  • Bleed. Front-to-back registration is never perfect. A border close to the trim on both sides makes any shift obvious, so keep critical elements inside a safe area and confirm the trim with the cutting marks and cut order you will actually use.

Centring the grid on the sheet is the simplest protection: a centred, evenly spaced grid mirrors onto itself, so a small flip mistake changes which back sits where but not whether it fits.

How do you proof a duplex cut stack before the run?

  1. Make a proof back. For static backs, temporarily add the item number in small type to each back page, then remove it for production. Now every back can be checked against its front.
  2. Print a short duplex run on the real stock, enough sheets to cross a pile boundary if your tool lets you print a range, using the exact flip setting planned for production.
  3. Check one sheet against the light. Each front number should sit over its own proof number. A pin pushed through the centre of each position on the front should come out inside the matching back position.
  4. Cut the proof stack and read every piece in each pile: the fronts count upward, and front and back numbers agree on every piece.
  5. Record the result: flip edge, paper orientation, tray and which face was up. Duplex behaviour can change with stock and tray, so repeat the check when either changes.

If the backs are in the right positions but upside down, the grid is right and the flip axis is wrong. If backs are upright but belong to the neighbouring position, the mirroring axis is wrong. If the pairing is right and the piles are wrong, the problem is the block arithmetic, not duplex.

How do you set up the file?

Start from a single-item PDF in final order, fronts and backs paired, with the item count padded so it divides by the number of positions. Choose the grid, gaps and sheet, then confirm how your imposition tool expects the backs: interleaved pages, a separate back file, or one repeated back. In PDFImpose, set up cut-and-stack order and check in the app how the layout treats reverse pages and which flip it assumes before exporting. Whatever tool you use, keep the exported PDF as the file that goes to the printer, and do not let the printer driver re-impose or re-rotate it. The cut and stack PDF planner covers the single-sided basics, and the cut and stack vs collated comparison helps when only some items need sequential piles.

Common questions

Does duplex halve the number of sheets in cut and stack?

Not when the back carries the reverse of each item. Each item still needs one position on the front and the same position on the back, so the sheet count equals the block size, the same as single-sided. What doubles is the number of printed sides and PDF pages, not the number of items per sheet.

Is long-edge or short-edge flip correct for tickets?

Neither is universally correct. The right setting depends on sheet orientation, whether the customer wants backs head to head or head to foot, and how the driver rotates the second side. Decide the reading direction first, then confirm the setting on a marked duplex proof.

Can every back be the same page?

Yes, and it is the safest arrangement when the design permits it. A single repeated back cannot be paired with the wrong front. You still need the back grid to align physically with the front, including any stub or panel that must fall in a particular place.

Why are my backs correct on the first sheet but wrong later?

Look at how the source file was built. If one item is missing a back page, or a back was duplicated, every later front and back shifts by one page in an interleaved file. Count pages per item before imposing; the total should be exactly twice the item count.

Should spoilage sheets be numbered on both sides?

Overs should carry complete, correctly paired fronts and backs so a damaged sheet can be replaced with a matching one. Continue the numbering past the target rather than repeating numbers, and confirm with the printer how overs are handled.

BEFORE YOU CHOOSE

Does PDFImpose fit this job?

Prepare an already numbered PDF for cutting into consecutive piles. Generate variable records before imposition.

What to verify

Print a short numbered test, cut it, and gather the piles in the intended order. Check partial batches and cutter capacity.

Plan the cut-and-stack blocks →

Account and export terms

Google sign-in is required. The free plan includes five lifetime exports, with eight hours between free exports. Pro is US$14.99/month or US$149.99/year, excluding tax.

View current PDFImpose plans →

This is a product-operated field guide in the PDFImpose network. Confirm the exported result and current terms before paying.