Mac OS 9 Print to PDF Workflows

Unlike Mac OS X, which featured native system-level PDF generation via its Quartz graphics layer, classic Mac OS 9 lacked a built-in "Save as PDF" engine. To convert documents into digital PDF files, users in the late 1990s and early 2000s relied on a combination of PostScript file generation, Adobe Acrobat software suites, Chooser extensions, and third-party virtual printer drivers.

The Adobe Acrobat Distiller Workflow

The industry-standard method for producing press-ready, high-fidelity PDFs involved a two-step PostScript conversion process:

  1. Print to PostScript File: Users selected standard PostScript printer drivers—such as Apple LaserWriter 8 or AdobePS—via the Chooser. From the standard print dialog, the destination was changed from "Printer" to "File." The user would select "PostScript Job" and specify a PostScript level (Level 2 or 3) along with the desired font embedding options to generate a .ps file on their hard drive.
  2. Process via Acrobat Distiller: The generated .ps file was then opened in Adobe Acrobat Distiller. Distiller interpreted the PostScript code, resolved graphics and fonts, and compiled the final .pdf document.

To automate this pipeline, production environments configured "Watched Folders" in Distiller. Users printed their PostScript files directly into an designated "In" folder on their Mac, and a background Distiller process automatically converted them and deposited completed PDFs into an "Out" folder.

Adobe PDFWriter

Included with standard retail packages of Adobe Acrobat (versions 3 through 5), Adobe PDFWriter was a virtual printer driver designed for speed rather than professional pre-press output.

Users selected PDFWriter directly inside the Chooser. Once selected, choosing "Print" from any standard application intercepted QuickDraw drawing commands and directly translated them into basic PDF structures without requiring an intermediate PostScript file. While fast and convenient for basic office documents, PDFWriter did not support Encapsulated PostScript (EPS) graphics, custom PostScript halftones, or advanced color separations, often leading to missing or low-resolution elements in complex layouts.

PrintToPDF (Shareware)

For users who did not own the expensive Adobe Acrobat package, third-party shareware utilities were common. The most widespread was PrintToPDF, developed by James Walker.

Operating similarly to PDFWriter, PrintToPDF installed as an extension and appeared as an option in the Chooser. It captured QuickDraw print calls and converted text, vector shapes, and standard PICT or bitmap images directly into a PDF file. It was lightweight, did not require Adobe software, and supported basic features like web hyperlinks, bookmarks, and custom page sizes.

Direct Export in Desktop Publishing Software

High-end publishing applications on Mac OS 9 offered proprietary internal workflows:

  • Adobe InDesign (1.x and 2.0): InDesign featured a direct "Export to PDF" function that bypassed the system print dialog entirely, utilizing an internal PDF library to generate files directly from the layout.
  • QuarkXPress (4.x and 5.x): Quark relied on the "PDF Filter" XTension. When activated, it automated the background handoff between Quark's print engine, the LaserWriter driver, and an installed copy of Acrobat Distiller to output a PDF in a single step.