Booklet page imposition order
An 8-page saddle-stitched booklet prints as 8, 1, 2, 7 on the outer sheet and 6, 3, 4, 5 on the inner one. Enter your page count and get the full printer sequence, each sheet's sides and the spreads a reader will see. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Pages
- 8
- Padded pages
- 8
- Blank count
- 0
- Sheet count
- 2
- Side count
- 4
A saddle-stitched booklet is assembled from stacked sheets that are folded once and stapled through the spine. Because each physical sheet carries four pages — two on the front and two on the back — the numbers that share a sheet are not neighbors in reading order. The outer sheet of an eight-page booklet holds pages 8 and 1 on the front and pages 2 and 7 on the back; after the fold those numbers land on the cover, the first opening, and the back cover. Getting that sequence wrong puts page 3 on the cover or mirrors a spread. This calculator accepts a content page count, pads it to the next multiple of four, and returns the classic outside-in printer imposition order, the left and right assignment of every sheet, and the reading spreads you should see once the booklet is folded. Padding slots are zeros so an imposer can drop in blanks without inventing extra numbered pages.
What saddle-stitch imposition is and why the order is not 1, 2, 3
Saddle-stitch imposition exists because a folded sheet is a four-page signature, not a stack of single leaves. Imagine one sheet printed landscape, flipped on the long edge, then folded in half: the front-right panel becomes the cover (page 1), the back-left panel becomes page 2, the back-right panel becomes the last-but-one page, and the front-left panel becomes the back cover. Stack another sheet inside and the same pairing repeats, walking inward two pages from each end.
The second sheet of an eight-page book therefore holds 6 and 3 on the front and 4 and 5 on the back — the center spread the reader sees when the booklet is opened all the way.
In general, if N is the padded page count (the smallest multiple of four that can hold every content page), sheet i counted from the outside with i starting at zero receives front left N minus 2i, front right 2i plus 1, back left 2i plus 2, and back right N minus 2i minus 1. That identity is what every desktop booklet printer, InDesign print-booklet command, and commercial 2-up imposer is computing when it asks for a printer sequence instead of reading order.
Content counts that are not multiples of four cannot fill every panel, so the remaining panels at the end of the book become blank. A six-page program is imposed as eight pages with pages 7 and 8 empty: the outer front is blank beside page 1, and the last opening shows page 6 beside a blank. This tool encodes exactly that convention and never invents a seventh content page.
What you can do with it
Programs and bulletins that are not a multiple of four
A 6- or 10-page event program is padded with trailing blanks (0). The shop inserts empty panels instead of inventing extra numbered pages.
FAQ
Why must a saddle-stitched booklet have a page count that is a multiple of 4?
Each physical sheet is printed on both sides, two pages per side, so it always carries four pages. Content counts that are not a multiple of 4 are padded with trailing blanks (0) to the next multiple of 4.
What is the printer imposition order for an 8-page saddle-stitched booklet?
The outside-in 2-up sequence is 8, 1, 2, 7, 6, 3, 4, 5. Sheet 1 is 8|1 on the front and 2|7 on the back; sheet 2 is 6|3 and 4|5 (the center spread).
Does this calculator handle perfect binding or several signatures?
No. It computes a single saddle-stitched signature (stacked sheets folded once). Perfect-bound books that gather several 16-page signatures, and creep compensation for thick books, are out of scope.
What happens if my booklet has 6 pages?
It is laid out as 8 pages with pages 7 and 8 left blank. The blanks show up as zeros in the sequence, so you can drop in empty pages without numbering extra ones.
How many pages can a booklet have in this calculator?
Any whole number from 1 to 200 content pages. A 200-page saddle-stitched booklet is already thicker than most print shops will staple, which is why the limit sits there.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/date/booklet-page-order \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"pages":8}'const res = await fetch("https://api.kit.forhosting.com/date/booklet-page-order", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"pages": 8
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/date/booklet-page-order",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"pages": 8
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/date/booklet-page-order", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"pages":8}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"pages":8}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/date/booklet-page-order", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"pages": 8
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "date.booklet_page_order",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Limits
max_pages | 200 |
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Successful requests are billed at the published $0.002; invalid input is not charged.
Input contract, response shape, and how to read the sequence
The value must be a whole number from 1 through 200 inclusive; 200 pages is fifty sheets and already thicker than most shops will saddle-stitch, which is the point of the ceiling. Digit strings that parse as integers are allowed so a form field or spreadsheet cell does not need a second conversion. Example: pages equals 6 yields the same skeleton with 0 in the slots that would have been 8 and 7. POST a JSON body with one required integer, pages, the number of content pages in the finished booklet. The field also accepts the aliases page_count, n, num_pages, and page_total. Missing pages, an empty string, a non-integer such as 8.5, zero, a negative count, or a value above 200 fail with invalid_input naming the field, and those failures are not billed. On success the body echoes pages, reports padded_pages as the next multiple of four, blank_count as how many trailing blanks were added, and sheet_count as padded_pages divided by four. print_order is the flat printer sequence of four numbers per sheet — front left, front right, back left, back right — walking from the outer sheet to the center, with 0 standing for a blank pad. print_order_text is the same list as a comma-separated string for paste into an imposition field. sheets lists each physical sheet with front_left, front_right, back_left, and back_right. reading_spreads lists the left and right pages the reader sees from the cover opening through the last interior spread after folding, which is the check that the imposition is correct. formula restates the sheet-i identity; method is saddle_stitch_2up. Example: pages equals 8 yields print_order 8, 1, 2, 7, 6, 3, 4, 5 and two sheets.
Where a booklet imposition order calculator earns its keep
Print shops, in-plant copy centers, and designers who export a reader-order PDF and then need a 2-up duplex run use a booklet page imposition order calculator so the copier does not have to guess. If the center opening is 4 facing 5 on an eight-page piece, the job is right; if it is 3 facing 6, the backs were mirrored and the flip edge was wrong. Event programs, church bulletins, school zines, and saddle-stitched lookbooks all hit the same arithmetic, and they hit it again whenever the editor adds a page and the count is no longer a multiple of four. Automation scripts in a RIP or a web-to-print storefront call the same contract instead of re-deriving the pairing. A typical desktop path is: take the print_order list, build an imposed PDF that places those page numbers two-up in that sequence, print duplex flipping on the long edge, fold the stack, and staple the spine.
Integration use cases
Desktop 2-up duplex of a reader-order PDF
Take an 8- or 16-page export, impose the returned print_order two-up, print long-edge duplex, fold, and staple. The center spread should read as consecutive pairs.
Web-to-print and RIP automation
Storefronts and prepress scripts freeze the print_order array as a golden so a refactor cannot silently swap fronts and backs on every saddle-stitched job.
Technical questions
What does 0 mean in print_order?
Zero is a blank pad page. If you send 6 content pages, the booklet is imposed as 8 pages and the slots that would have been pages 7 and 8 are 0 so the imposer inserts empty panels.
What does the booklet page imposition order calculator cost?
The in-browser runner is free and uses the same library as the API. Successful API requests are billed at $0.002 from prepaid KIT balance; invalid input is not charged.