--- title: "What Is Desktop Publishing and When Should You Use It?" description: "Desktop publishing is production, not design: styles, parent pages and threaded frames that make decisions repeatable, and a PDF that is only the export." canonical: "https://freeaigeneration.com/en/guides/what-is-desktop-publishing-and-when-should-you-use-it/" robots: "noindex" lang: "en" --- # What Is Desktop Publishing and When Should You Use It? Desktop publishing is the part of publishing that composes the page rather than deciding what goes on it. The writing is finished, the photographs are chosen, and the work becomes a grid, a set of styles and frames of text that flow from one page to the next. The phrase "desktop publishing and when should you use it" hides two questions behind one piece of jargon. The first is what the discipline actually produces. The second is which deliverable you owe at the end, because desktop publishing is one of the few activities where the editable file and the finished file are genuinely different objects. ## Production, not design Design makes decisions. Production makes those decisions repeatable. A designer chooses a typeface and a tone; production decides that body text carries a named paragraph style, that captions carry a second one, that a chapter opening always breaks to a new page. That distinction explains the tooling. Page layout software is full of mechanisms for repetition, because a magazine or a catalogue is the same decisions applied forty times without drifting. When the decision changes, you change it once and the document follows. ## What composed pages contain A composed document holds more than boxes of text. Parent pages supply elements that repeat on every page — a running head, a folio, a background rule — so you edit one place rather than forty. Paragraph and character styles store type decisions and apply them by name. Threaded text frames pour a single story through several pages, so an edit on page two can push a line onto page three. Colour swatches let a named colour be changed everywhere at once. Text wrap keeps type clear of images without manual nudging. None of that survives in a PDF. A PDF is a page description format standardised as ISO 32000, arranged as a page tree of content streams and resources. It records where marks fall on a fixed canvas. Parent pages, styles and text links exist only in the source document. ## Why the file you keep is the layout file If the deliverable will be revised, the layout file is the one that matters. A reprint with a corrected price, a translation into another language, a new edition with two extra pages — each of those is a change to the structure, and structure lives in the source. The PDF is the export. It is what goes to a printer, a client or a reader, and it is deliberately fixed so that nobody's copy silently reflows. That fixity is a feature for the recipient and a dead end for the author, which is the whole reason the two files exist. PDF/X, the print-exchange family standardised as ISO 15930, belongs to the export side too. It constrains what a PDF may contain so a press can consume it predictably. It is not a format you compose in. ## A pica is twelve points Measurements in page layout are not in millimetres by default. A pica is 12 points, a sixth of an inch, or 4.233 mm. An A4 page is 49.6 × 70.2 picas, which is why a layout application will happily ask for a margin of 12p rather than 50.8 mm. Facing pages change the arithmetic in a useful way. A 16-page document set as facing pages is 8 spreads, not 16 individual pages, because the unit of work becomes the pair of pages a reader sees at once. A 32-page booklet imposed in eight-page signatures is 4 signatures, and that number comes from paper and folding rather than from design preference. Knowing the count early matters, because signatures are decided before the document is finished and they constrain the page count you can add later. ## Where the browser editor fits The [Page Layout Editor](/en/tools/page-layout-editor/) implements the composition model rather than a simplified sketch of it: multi-page documents, spreads, parent pages, threaded text frames, paragraph and character styles, colour swatches and text wrap. Geometry is entered in picas, with Facing Pages and Adjust Layout governing how frames respond when the page changes size. Save writes a .designcraft file and exporting a page produces a PNG, both through the browser's download. The edges are equally specific. Upstream describes the project as pre-alpha with a published gap list, the interface is English only, and it is built for desktop browsers rather than phones or tablets. There are no cloud documents, so a tab closed without saving loses unsaved work. The upstream project documents PDF/X-4, PDF/A-2b, EPUB and IDML, but none of those was verified in this build, and there is no evidence at all for bleed, crop marks, CMYK or preflight. This is not a professional page-layout replacement. What that leaves is a genuine place to learn and to work: compose the pages, set the styles, thread the text, and treat the layout file as the source. ## Two assumptions worth dropping The first is that desktop publishing means graphic design. It means production, and plenty of people who can produce a clean 32-page document could not draw a poster, and the reverse is just as true. The second is that the PDF is the source. Once that idea takes hold, every correction becomes a patch on a fixed page and the document slowly loses its structure. The distinction is worked through in [PDF editor versus page layout editor](/en/guides/pdf-editor-vs-page-layout-editor-which-do-you-need/), and the handoff side of it sits in [preparing a print-ready PDF](/en/guides/how-to-prepare-a-print-ready-pdf/). Both are part of the [guides hub](/en/guides/) if you are building a document from first page to press.