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

Cut and Stack Imposition Explained (With Visuals)

Answer first Cut and stack imposition places a sequential block of pages in each position on an N-up sheet instead of repeating one page. On a 400-page, 4-up job, position 1 carries pages 1-100, position 2 carries 101-200, and so on. A single guillotine cut through the printed stack then produces four piles that are each already in page order, with no manual collating step. The arithmetic follows from that: the block size is the total page count divided by the number of positions, so the scheme works cleanly when the count divides evenly and needs padding when it does not. Everything depends on the stack staying in printed order from press to cutter, because the ordering lives in the sequence of sheets rather than in anything printed on them. Reshuffling the stack, or cutting before the full run is printed, destroys the sequence in a way that is difficult to detect afterwards.

What is cut and stack imposition?

Cut and stack imposition is a page layout method used when a job prints many small, individually distinct items — tickets, coupons, flashcards, numbered forms — on one larger press sheet. Rather than repeating the same design in every position (which is how business cards or postcards are usually imposed), each position on the sheet holds a different, sequential range of pages from the source document.

The name describes the bindery step exactly: the printer cuts the stack of sheets once, and the resulting piles are already stacked in the correct order. There is no secondary collating pass where an operator interleaves loose sheets by hand or runs them through a collator. That is the entire value of the technique — it turns collating into a byproduct of cutting.

400-ticket, 4-up cut and stack layout A press sheet divided into a 2x2 grid. Each quadrant is labeled with its position number and the sequential page range it carries: position 1 pages 1-100, position 2 pages 101-200, position 3 pages 201-300, position 4 pages 301-400. POSITION 1 pages 1–100 → cut stack A (1..100) POSITION 2 pages 101–200 → cut stack B (101..200) POSITION 3 pages 201–300 → cut stack C (201..300) POSITION 4 pages 301–400 → cut stack D (301..400)
Fig. 1 — A 400-page ticket job on a 4-up sheet. Each of the 100 sheets prints one ticket from each block; cutting the pile once yields four piles already numbered 1–100, 101–200, 201–300, and 301–400.

Look closely at what makes position 1 different from a normal repeated layout: it does not hold "ticket #1" on every sheet. It holds ticket #1 on sheet 1, ticket #2 on sheet 2, ticket #3 on sheet 3, and so on through ticket #100 on sheet 100. The same is true for the other three positions, each starting from its own offset. Print 100 sheets, cut once, and you lift four complete, ordered stacks off the table.

How does a cut and stack sheet get built?

The math is simple division. Take the total number of unique pages in the job and divide by the number of positions on the sheet — that gives the pages-per-stack figure, which is also the number of sheets you need to print. Each position is then assigned a contiguous block of that size, offset by its index.

For the 400-ticket, 4-up example: 400 ÷ 4 = 100 pages per stack, so the press run is 100 sheets. Position 1 starts at page 1, position 2 starts at page 101 (1 + 100), position 3 starts at page 201, and position 4 starts at page 301. The table below shows how this scales across a few common N-up values for the same 400-page job.

N-upSheets printedPages per stackPosition 1 rangeLast position range
2-up2002001–200201–400
4-up1001001–100301–400
8-up50501–50351–400
10-up40401–40361–400

Notice the trade-off: more positions per sheet means fewer sheets to print, but also more distinct cut piles to manage at the end, and a tighter sheet layout to fit within the press's maximum sheet size. Most ticket and coupon jobs land somewhere between 4-up and 10-up depending on the finished trim size and the press sheet available.

Why does the order live in the stack rather than on the sheet?

Nothing printed on an individual sheet records its position in the sequence. Sheet forty of a run looks exactly like sheet four, and the only thing that makes the piles come out in order is that the sheets are still in the order the press produced them.

That single property explains most of the operational rules around cut and stack. The stack must not be shuffled, riffled or split between operators, the job cannot be cut until the whole run is printed, and a damaged sheet cannot simply be reprinted and dropped back on top.

It also explains why the failure is so expensive. A stack that has lost its order cannot be reconstructed by inspection, because there is no information on the sheets to reconstruct it from, so the usual remedy is to reprint rather than to sort.

What does the press operator see on the sheet?

Very little that identifies the job's position. A cut and stack sheet looks like an ordinary N-up sheet, and the numbers in its positions are the only clue that the pages are widely separated rather than consecutive. Nothing on the sheet says which sheet of the run it is.

That is why the run is managed as a physical object rather than as a set of files. The lift stays together, the delivery is kept in order, and a sheet pulled for inspection goes back exactly where it came from rather than on top.

Spoilage is handled by overprinting rather than by patching. Because a replacement sheet cannot simply be dropped into the middle of a stack, most shops run extra sheets at the start and accept the waste as cheaper than a lost sequence.

How does the lift height limit the run?

A guillotine can only cut so deep, so the stack is cut in lifts rather than in one pass, and each lift has to be taken from the top of the pile in order. The cutting height of the machine, not the length of the run, decides how many lifts a job needs.

This matters because every lift boundary is an opportunity to lose the sequence. Lifts are kept in order and cut in order, and the piles from each lift are stacked onto the piles from the previous one rather than beside them.

Heavier stock reduces the sheet count per lift, so the same run on a thicker sheet needs more lifts and more handling. That is a scheduling consideration as much as a technical one, since the extra handling is where sequence errors are introduced.

Common questions

Does cut and stack imposition require special press equipment?

No. Cut and stack is a layout decision made before printing, not a press feature. Any digital or offset press that can print an N-up sheet can produce a cut and stack job; the only bindery requirement is a single guillotine cut through the printed pile.

What happens if the piece has bleed on all sides?

Bleed still works the same way — each position keeps its own bleed and trim marks. The only change is that adjoining positions need a double cut (a thin slice removed between them) so bleed from one item doesn't show as a sliver on its neighbor.

Can cut and stack be combined with variable data numbering?

Yes, and it is the standard way to print sequentially numbered tickets. The numbering is applied per page before imposition; the cut and stack layout then guarantees the printed numbers stay in order once the stack is cut. See our numbered tickets guide for a worked example.

Is cut and stack the same as a "step and repeat" layout?

No. Step and repeat places the identical single page in every position on the sheet, which is fine for uniform items like blank business cards. Cut and stack places a different sequential page in each position, which is required whenever the finished pieces must differ and stay in order.

What happens if the printed stack gets shuffled?

The sequence is lost, and usually unrecoverably. In cut and stack the ordering lives in the depth of the stack rather than in anything printed on the sheet, so there is no way to reconstruct it by inspection. Keep the stack in printed order from press to cutter and cut only after the full run is printed.

What if the page count does not divide evenly?

Pad it. The scheme needs an equal block in every position, so an uneven count leaves one pile short and shifts the boundaries. Adding blank or duplicate pages to reach a divisible total is the normal fix, and it is cheaper than discovering the mismatch after cutting.

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.