PDF to PostScript

The PDF to PostScript API Tool converts a PDF document into a PostScript (.ps) file through the /postscript endpoint. It is intended for print, prepress, publishing, and legacy production workflows that require PostScript output or use PostScript as an intermediate format.

The API creates a separate PostScript resource. It does not alter or replace the original PDF, so applications can retain the source document and use the generated .ps file only where it is needed.

The tool supports valid single-page and multi-page PDF documents containing text, raster images, vector graphics, or mixed page content. It can convert an entire document or selected pages, and printable annotations can be included or omitted.

The generated PostScript represents the PDF’s printable page content. PDF-specific features such as tags, layers, attachments, interactive forms, and other document-level structures are not preserved as interactive PostScript features.

PostScript remains part of many print, prepress, publishing, and legacy document-production environments. A PDF may need to be converted when a printer, RIP, production application, or downstream system expects PostScript input.

Common uses include:

• Preparing PostScript delivery files for print production.
• Feeding existing RIPs and legacy publishing systems.
• Adding a PostScript stage to an automated prepress workflow.
• Creating an intermediate file for PDF refrying.
• Supporting established systems that cannot accept PDF directly.

Yes. Upload a local PDF with file, or submit the id of a PDF already stored as a pdfRest resource. Send one input method per request.

Using a resource ID makes it possible to connect PDF to PostScript with other pdfRest API Tools. An application can pass the output from an earlier operation directly into /postscript without downloading and uploading the intermediate PDF.

A successful request returns a PostScript resource with a .ps filename, resource ID, and download information. The default output name is [INPUT_FILE_NAME]_pdfrest_postscript, or you can use output to provide a different base filename.

The returned resource ID can be passed to subsequent pdfRest requests. This allows applications to keep intermediate files within a managed API workflow instead of transferring them through local storage.

The API supports PostScript Level 2 and PostScript Level 3. PostScript Level 3 is used by default.

Select Level 2 when a downstream RIP, printer, or legacy application requires that compatibility level. Select Level 3 when the target production environment supports more current PostScript output.

Yes. The page_range parameter can convert the complete document, one page, or a combination of individual pages and ranges. The default value is all.

Examples include:

• 1 to convert only page 1
• 1,3-5 to convert pages 1, 3, 4, and 5
• 14-last to convert page 14 through the final page

This is useful for preparing covers, inserts, proof pages, production samples, or other targeted deliverables without first creating a separate PDF.

The API provides controls for adapting PostScript output to different production requirements:

• Use ps_level to select PostScript Level 2 or Level 3.
• Use page_range to select the pages to convert.
• Use binary_output to choose binary or text-safe, 7-bit PostScript.
• Use scale to enlarge or reduce page content.
• Use rotate to rotate output pages.
• Use shrink_to_fit to reduce content to fit the output page.
• Use print_annotations to include or omit printable annotations.
• Use output to customize the generated filename.

These controls help one application serve printers, RIPs, transfer channels, and legacy systems with different PostScript requirements.

Binary PostScript is the default and can include binary data where supported. It is appropriate for systems and transfer paths that accept binary PostScript directly.

Set binary_output to false when a downstream application or transfer process requires text-safe, 7-bit PostScript. This can improve compatibility with older systems that cannot reliably transport binary data.

Printable PDF annotations are included by default. Set print_annotations to false when comments, stamps, markups, or other printable annotations should not appear in the generated PostScript.

This allows one workflow to include review marks for proofing while another produces a clean production artifact from the same source PDF.

PostScript is a page-description format rather than an interactive document format. The conversion represents printable page content but does not preserve PDF-specific features such as tags, layers, attachments, interactive forms, or document navigation as equivalent interactive PostScript structures.

Keep the original PDF whenever those features must remain available. The generated PostScript should be treated as a production or delivery derivative rather than a replacement for the source document.

PDF refrying is a PDF -> PostScript -> PDF roundtrip. Some established print and prepress workflows use it to create a PostScript-based delivery derivative or rebuild page content for a downstream requirement.

Use PDF to PostScript to create the intermediate .ps resource, then pass that resource to Convert to PDF for the return conversion. Convert to PDF can optionally apply an Adobe Distiller-compatible .joboptions profile during the PostScript-to-PDF step.

Refrying can discard PDF-specific features such as tags, forms, layers, annotations, and other structural or interactive content. Preserve the original PDF and use the generated derivative only where the downstream workflow accepts those tradeoffs.

pdfRest combines Adobe technology, production-ready output controls, and a scalable REST API workflow. Developers can automate PostScript creation without maintaining separate desktop applications or conversion infrastructure.

The API supports complete documents and selected page ranges, PostScript Level 2 and Level 3, binary and text-safe output, page-handling controls, annotation printing, managed resource IDs, and integration with Convert to PDF for PDF refrying workflows.

Security and privacy are priorities at pdfRest. The platform supports enterprise security and compliance requirements, including GDPR and HIPAA. Files are encrypted during transit and at rest and are permanently deleted after the applicable retention period, which is 30 minutes for most plans.

For complete details, review the pdfRest Data Processing Agreement.

pdfRest provides dedicated European Union processing endpoints for organizations that need their document processing to occur within the EU. Send the PDF-to-PostScript request to the EU service endpoint to keep that API operation within the applicable EU processing environment.

A GDPR usage fee may apply to some plans. Review the pdfRest Data Processing Agreement for details about processing, retention, subprocessors, and data-protection responsibilities.

Call the /postscript endpoint with either a PDF upload or an existing PDF resource ID. The endpoint supports multipart requests for local file uploads and JSON requests for existing resources.

Use API Lab to test the operation and generate a request example. The API Reference documentation provides the complete request and response contract.

Yes. pdfRest offers two self-hosted deployment options.

The pdfRest API Toolkit on AWS lets organizations deploy and manage the API within their AWS environment with pay-as-you-go pricing through AWS Marketplace.

The pdfRest API Toolkit Container provides greater environmental control through a Docker container that can run in an on-premises data center or public or private cloud environment under a custom licensing model.