The rendered file is the thing you upload. It is not the thing you keep.
Plenty of publishing jobs ask for the same puzzles again in a different shape: a large-print edition at a bigger trim, a themed slice cut down for a printables listing, one page pulled out for a newsletter, a corrected reprint. Whether those are a re-render that takes minutes or a rebuild that takes an evening is decided by one thing — what you saved when the first book was done.
One job a saved project does not cover is worth naming early, because it is the one people expect: a restored project rebuilds the book you already made, not a new one. The next volume in a series needs fresh puzzles, and fresh puzzles come from a generation run, not from reopening the last book. What the project saves you there is the setup around them — the layout, the titles, the structure — so the second volume is an evening of generating rather than an evening of generating and rebuilding a book from scratch.
The render is the output; the project is the asset
A finished interior is the end of a chain: generate the puzzles, assemble them into a book, review, render. Each step produces something, and only two of them produce something reusable. The puzzle and solution images are files on disk. The assembly — which puzzles, in what order, under which layout, with what titles — is the part that carries every judgment you made, and it is the part that vanishes with the session if it is never written down.
That is why a re-render is cheap and a regeneration is not. Regenerating means finding the same word lists, setting the same grid size and difficulty, and hoping the run comes back looking like the one you shipped. Restoring means opening a file. For how the two book builders differ before you ever save, see Puzzle Book Studio vs Instant Puzzle Books.
What the project file carries
In Puzzle Book Studio, Save Project on the toolstrip writes a .pmpbook file — an indented JSON envelope holding the project and the active book layout, saved by default into Documents\BookPublisherTools\Presets\PMP\IPB-Project. Restore Project reads one back, swaps it into the session, and reassembles the book from it.
What travels inside is the composition, not the pages:
- Per collection — the title and description, the difficulty names you renamed, whether the collection is hidden, whether it starts on a new page, the puzzle cap if you set one, the page layout and puzzle-slot settings, the puzzle type, grid size, difficulty level and the quantity that was requested.
- Per puzzle — the puzzle image, the solution image, any secondary image, the word lists, the title and description you typed, and whether that puzzle is hidden or flagged for a human pass.
- The whole book layout — trim, margins, typography, the content-page settings, the output settings.
Pagination is the part it rebuilds rather than stores: the assembler regenerates the pages on restore from the settings the file carries. That is the useful half of the design — change the trim on a restored project and the book re-paginates around the same puzzles, because the page numbers were always derived rather than saved.
Two practical habits follow. Save the project before you render, and save it again once the review below is clean — a saved project with warnings still in it restores with the same warnings. And save a separate copy when you are about to cut a different product out of it, because restoring replaces the session you have open.
The images live beside the file, not inside it
Each puzzle in the project points at its image by file path. That keeps the project file small and it makes the folder of rendered images part of the asset rather than a by-product. Move one without the other and the book comes back short.
The software checks this for you rather than letting it surface in the render. On restore, every render is validated against disk: the puzzle image is required, and the solution image is required wherever the slot calls for one. Anything missing is hidden from the assembled book and listed in the Warnings panel, so a restored project tells you what it could not find instead of quietly printing fewer pages. A puzzle you had already hidden on purpose stays hidden — your choice outranks the file check.
The repair is built into the same panel. Clicking a missing-asset warning opens Resolve missing puzzle files, where each image can be re-pointed by hand — or, if the whole folder moved, Locate Folder… takes the new folder, matches every file it can by name including through subfolders, re-points them in one pass and rebuilds once. Names that could match more than one file are left for you to pick, and anything still outstanding stays in the warnings list.
Clear the warnings before you render
The warnings panel is the review step that a page-through does not replace, because it reports things the eye slides past. Alongside missing assets it raises a word list that has outgrown its space, a word list that only fits because its font shrank, a puzzle flagged as needing a human pass, and a content page whose text runs past the page. Clicking any of those warnings jumps the Studio to the page in question.
This matters most exactly where people expect it least. Enlarging type for a large-print edition is how word lists overflow; rewriting a title is how a description stops fitting. You want those found while the fix is a setting, not after a proof copy arrives.
The book keeps itself current while you work: an edit triggers one background rebuild about a second after the last change in a burst, and the status line above the preview reports where the book stands — Book changed — rebuilding shortly…, Rebuilding book…, or Rebuild failed — press Rebuild Book to retry. Read that line before you render. A book that is mid-rebuild is not the book you are about to export.
Render, then re-render
Render Book becomes available once the assembled book has pages, an output folder and base file name are set, and Output Settings has at least one format ticked. The everyday exports are page images, a PDF built from the puzzles, an image PDF built from the page images, and a slide deck; the multi-format rendering tutorial walks the export itself.
Three mechanics are worth knowing before the first long run. The export reports progress on the status line page by page and can be stopped: cancelling stops between pages, removes a partly written slide deck, and leaves the page images already written where they are. Page images land in a Pages/ folder that is emptied at the start of every render, so treat it as output rather than storage. And while an export runs, everything that could change the book underneath it — Book Settings, Rebuild Book, Save Project, Restore Project, the shuffle buttons, the properties cards, the warnings list — is held, because the export reads the live book as it goes. Navigating and selecting stay available throughout.
Once that run is clean, the second deliverable is a restored project, a changed setting and a second Render Book. That is the whole return on saving it.
Which builder, and what the license covers
Every puzzle module includes Instant Puzzle Books — settings first, then build. Puzzle Book Studio Creative gives the full book editing across one puzzle collection. Puzzle Book Studio Productivity gives the same editing across several collections combined into one book, which is the rung that matters when the interior is assembled from more than one run. The Studio tutorials cover the editor screen by screen, and how Puzzle Maker Pro works is the platform-level walkthrough if you are still mapping the stages.
A recurring single-page deliverable — a newsletter corner, a weekly worksheet — saves its state one level down, as a module preset rather than a book project. Same principle, smaller file: the setup happens once and each issue is a regenerate and an export.
Every paid Puzzle Maker Pro edition lets you sell the finished books, worksheets, and packs you make to your own readers and customers. Productivity adds the right to sell or supply the generated puzzles to other publishers and sellers. Saving and re-rendering a project you already own changes neither of those.
The one decision this workflow hands back to you is where the file goes. Each marketplace publishes its own current rules on interior specification, content and the licensing wording a listing has to carry, and a newsletter or magazine answers to its own publisher’s editorial rules. Read those on the platform itself, at the time you upload. That check belongs to the listing, not to the render.
The whole point
Treat the .pmpbook and its image folder as the product and the PDF as a print of it. Save the project before you render and again once the warnings panel is empty. Keep the images with the file, and use Locate Folder… when they move. Then the second trim, the cut-down pack and the corrected reprint are each a restore, a setting and a render — and the next volume starts from a book you can rebuild rather than a folder of images you have to re-explain to yourself.
Other puzzles you might like
If trim changes are the main reason you are saving projects, large-print puzzle books on KDP walks the typography and layout choices that tend to trigger warnings when you scale a book up. It pairs well with this page because the fix is almost always a restored project and a second render, not a new generation run.
When the same interior needs to ship as a paperback and as single-page printables, turn a KDP puzzle book into Etsy printables explains how one saved book job can feed both channels if you kept the project and the image folder together.
For the builder choice and edition split before you commit to Studio, Puzzle Book Studio vs Instant Puzzle Books is the comparison page — Instant Puzzle Books for uniform whole-book output, Studio when you need page-level control or a multi-collection interior on Productivity.