ghostscript.com No paid content found

Ghostscript can be integrated in two ways: as a standalone command line application, or as an SDK embedded directly into your own application. It is written entirely in C and runs on most operating systems and platforms, including Windows and macOS, which makes it suitable for server-side PDF generation pipelines and SaaS document workflows. The right choice depends on whether you want to call an external process or link the interpreter into your own code.

The Two Integration Paths

Standalone command line application

You invoke Ghostscript as a separate process and pass it input files and options. This is the simplest path when your workflow already runs shell commands, scheduled jobs, or a build/processing pipeline.

• Input: a PostScript or PDF file, plus the output format and options you specify.
• Action: the Ghostscript executable interprets the input and renders, converts, or compresses it.
• Expected result: an output file in the target format (raster, vector, or optimized PDF), produced without changing your application's codebase.

This approach fits batch jobs such as document archiving, thumbnail generation, or pre-press processing, where a job runner can call the tool per file.

SDK integration

Ghostscript can be integrated with your application directly as an SDK. Instead of spawning a process, your application links against the interpreter and graphics library. This is the better fit when you need tight control over the conversion inside a long-running service, such as a SaaS document workflow handling many requests.

Because the code is written entirely in C, it can be embedded in C and C-compatible environments and built for the platforms listed above.

What You Can Build With It

The documented solution areas map directly onto integration scenarios:

If your goal is specifically standards-based e-invoicing, Ghostscript embeds structured XML invoice data into PDF/A-3 documents to generate ZUGFeRD and Factur-X compliant e-invoices.

Choosing the Right Product Component

Ghostscript is not a single binary; the family includes several interpreters built on the same graphics library. Which one you integrate depends on the input formats you must handle.

• Ghostscript — interpreter for the PostScript language and PDF files, consisting of a PostScript interpreter layer and a graphics library.
• GhostPDF — the PDF interpreter written entirely in C, now enabled as the default and also available as a standalone, PDF-only binary.
• GhostPCL — interpreter for PCL and PXL files, built on the Ghostscript graphics library.
• GhostXPS — interpreter for XPS (XML Paper Specification) files.
• GhostPDL — the entire Ghostscript family of products brought together, including all four elements.
• Ghostscript Office — a commercial version of GhostPDL that can also read and process common office documents including Word, PowerPoint, and Excel.

For a workflow that only handles PDF, the standalone GhostPDF binary keeps the integration surface small. If you must accept multiple page description languages, GhostPDL or Ghostscript Office covers more input types, with Office adding Word, PowerPoint, and Excel at commercial terms.

Practical Considerations Before You Integrate

• Deployment model: decide between calling an external process (easier to isolate and upgrade) and linking the SDK (lower per-call overhead, tighter control).
• Platform coverage: confirm your target OS is among those supported — the code runs on most operating systems and platforms, including Windows and macOS.
• Output requirements: if you need PDF/A for archiving or ZUGFeRD/Factur-X for e-invoicing, plan for those output profiles from the start rather than converting later.
• Extraction needs: if your workflow also requires parsing or extracting content from documents, the site points to MuPDF as a complementary lightweight parsing solution compatible with Python, .NET, JavaScript, C#, and more.

Where to Start

Download the component that matches your input formats, then choose the integration path: call it as a command line application for pipeline and batch use, or integrate it as an SDK for embedded, in-process conversion. For commercial needs such as office document input, contact the vendor about Ghostscript Office.

A PDF invoice in legal billing is a fixed-format document that presents the fees and costs owed on a matter in a layout that looks the same on every device. It is the digital equivalent of a printed bill: readable, portable, and easy to attach to an email or upload to a client portal. Its main limitation is that it is not machine-readable in the way a LEDES file is, so a client's e-billing system cannot automatically ingest it. PDF works best for flat-fee matters, small or one-off engagements, and clients who do not run an automated billing platform.

What "PDF" means in a legal billing context

When a billing tool offers to send an invoice "in PDF," it is generating a rendered document rather than a structured data file. The distinction matters:

• PDF is a presentation format. A human reads it. Line items, totals, and matter details appear as text and tables on a page.
• LEDES (Legal Electronic Data Exchange Standard) is a structured, delimited text format. An e-billing system parses it, validates it against outside counsel guidelines, and routes it for review.
• Email delivery is a transport method, not a format. You can email a PDF, email a LEDES file, or email a link to an online invoice.

These three are often confused because a single invoice can combine them: a LEDES file delivered by email, or a PDF attached to an email. The format is what the client's systems can read; the delivery method is how it arrives.

When a PDF invoice is the right choice

PDF is usually appropriate when the client does not require electronic submission through a billing platform. Common scenarios:

• Flat-fee and fixed-price matters. When the invoice is one or two lines, a structured file adds no value.
• Small businesses and individuals. Clients without an accounts payable system can open a PDF and pay from it.
• Retainers and replenishment requests. A simple statement of the retainer balance is easy to read as a PDF.
• Pro bono or courtesy bills. Where no formal e-billing review applies.
• Backup documentation. Even when a LEDES file is submitted, a PDF is often attached for the reviewer's convenience.

If the client has outside counsel guidelines requiring LEDES submission, a PDF alone will typically be rejected or returned for manual entry. Check the client's billing requirements before choosing the format.

PDF versus LEDES versus emailed invoice: a quick comparison

Core elements of a compliant legal PDF invoice

A PDF invoice should stand on its own. If a client's AP department picks it up with no context, it should still answer who, what, when, and how much.

Firm and client identification

• Firm name, address, and contact details
• Tax or VAT identification number where applicable
• Client name and billing contact
• Invoice number and invoice date
• Client matter number or reference

Matter and timekeeper detail

• Matter name and description
• For each timekeeper: name, initials, and billing rate
• Time entries with date, narrative description, and time recorded in tenths of an hour
• Clear separation of fee earners if rates differ

Fees, expenses, and totals

• Fees subtotal
• Disbursements and expenses, itemized with dates
• Taxes applied
• Prior payments, credits, or trust retainer applied
• Total amount due and currency

Payment terms

• Due date and payment window
• Accepted payment methods
• Remittance details or a payment link
• Late-payment terms if the engagement letter specifies them

A useful test: hand the PDF to someone who has never seen the matter and ask them to confirm the amount due and the period covered. If they hesitate, the invoice is missing something.

Practical limitations to plan around

PDF invoices shift work to the recipient. Someone at the client has to read the document and key the data into their system, which introduces delay and transcription errors. PDFs also cannot be validated against billing guidelines automatically, so a reviewer may reject a line item that a LEDES rule would have caught before submission.

Two habits reduce the friction:

1. Send a consistent template. Clients learn where to find the total, the matter number, and the payment terms.
2. Keep a LEDES version in reserve. If a client later adopts an e-billing platform, you can convert rather than rebuild.

Choosing between PDF, LEDES, and email delivery

Work from the client's requirements backward:

• Does the client mandate LEDES submission? If yes, PDF is a supplement, not a substitute.
• Is the matter flat-fee or very small? PDF is usually sufficient.
• Does the client have no billing system? PDF delivered by email or portal is the simplest path.
• Is the invoice complex with many timekeepers and expenses? A structured format reduces disputes, even if the client accepts PDF.

When in doubt, ask the client's billing contact which format they prefer and whether a PDF attachment is acceptable alongside any required file. That one question prevents most rejected invoices.

Easy Legal Billing supports sending or scheduling invoices in LEDES, email, or PDF formats, which lets you match the format to each client's requirements rather than forcing one approach across every matter.

Ghostscript's core interpreters — Ghostscript, GhostPDF, GhostPCL, GhostXPS, and GhostPDL — are all available for download directly from ghostscript.com. Ghostscript Office, the commercial edition that adds Word, PowerPoint, and Excel processing, is not a self-serve download; you reach it through the Contact Us route. The same page also links out to ZUGFeRD/Factur-X e-invoicing information and to MuPDF for advanced PDF extraction.

Download entries by product

If you only need PDF handling, GhostPDF is the focused choice and is already the default interpreter inside Ghostscript. If you need to cover several page description languages in one integration, GhostPDL bundles them.

Contact channels and adjacent options

• Contact Us — the entry point for Ghostscript Office and for commercial or integration questions.
• ZUGFeRD / Factur-X — Ghostscript generates ZUGFeRD and Factur-X compliant e-invoices by embedding structured XML invoice data into PDF/A-3 documents. The page offers a Learn More link plus a Contact Us option for standards-based, automated e-invoicing workflows.
• MuPDF — if your need is advanced PDF extraction rather than conversion, the page points to MuPDF as a fast, lightweight document parsing solution compatible with Python, .NET, JavaScript, C#, and more.

What to check before you download

• Integration style: Ghostscript can be called as a standalone command-line application or integrated directly into your application as an SDK. Decide which you need before picking a package.
• Platform: Ghostscript is written entirely in C and runs on most operating systems and platforms, including Windows and macOS. Confirm your target environment is covered.
• Feature scope: the feature set spans imposition, color management, native rendering to raster, conversion to vector formats, and custom screening technologies for color reproduction and print output. Match these against your pipeline before committing.

Typical use cases these downloads serve

The solutions listed on the page give a quick way to tell whether you are in the right place: server-side PDF generation pipelines, conversion and compression for SaaS applications, document archiving systems (PDF/A conversion), thumbnail and preview generation for document management, e-invoicing (ZUGFeRD/Factur-X), and pre-press and print production workflows.

Ghostscript is the core PostScript and PDF interpreter, while GhostPDF, GhostPCL, and GhostXPS are format-specific interpreters built on the same graphics library, and GhostPDL bundles all of them together. Choose based on which file formats you need to process: PDF and PostScript only (Ghostscript), PDF only (GhostPDF), PCL/PXL (GhostPCL), XPS (GhostXPS), or everything at once (GhostPDL).

The Ghostscript family at a glance

How the pieces relate

Ghostscript is not a single monolithic tool but a family of interpreters sharing one graphics library. That shared foundation is why the format-specific builds behave consistently for rendering, color management, and output.

• Ghostscript handles the two original page description languages: PostScript and PDF. It is the interpreter most people mean when they say "Ghostscript."
• GhostPDF is a newer, PDF-only interpreter written entirely in C. It is now the default PDF interpreter inside Ghostscript, and it is also distributed as a standalone binary for workflows that only touch PDF.
• GhostPCL and GhostXPS extend the same graphics library to PCL/PXL and XPS files respectively, so you can convert or render those formats without a separate rendering engine.
• GhostPDL is the umbrella build: it includes all four elements (Ghostscript, GhostPDF, GhostPCL, GhostXPS) in one package.

Which one should you choose?

• Working with PDF and PostScript? Use Ghostscript. It covers both, and its default PDF interpreter is now GhostPDF.
• Only processing PDF, and want the smallest surface? Use the standalone GhostPDF binary.
• Receiving PCL or PXL from print workflows? Use GhostPCL.
• Handling XPS documents? Use GhostXPS.
• Need to support several of these formats in one deployment? Use GhostPDL, which bundles the whole family.
• Need to read Word, PowerPoint, or Excel as well? That requires Ghostscript Office, the commercial version of GhostPDL.

Where these fit in real workflows

The Ghostscript family is used for server-side PDF generation pipelines, conversion and compression for SaaS applications, document archiving (PDF/A conversion), thumbnail and preview generation for document management systems, e-invoicing (ZUGFeRD/Factur-X), and pre-press and print production. ZUGFeRD and Factur-X support works by embedding structured XML invoice data into PDF/A-3 documents.

Integration is flexible: Ghostscript can be called as a standalone command line application or integrated directly into your application as an SDK. Because it is written entirely in C, it runs on most operating systems and platforms, including Windows and macOS.

If your need is advanced PDF extraction rather than conversion, the site points to MuPDF, a separate lightweight document parsing solution compatible with Python, .NET, JavaScript, C#, and more.

Ghostscript is an interpreter for the PostScript language and PDF files, made up of a PostScript interpreter layer and a graphics library. You use it to convert, compress, and render page description languages (PDLs) and document formats—natively handling PDF, PostScript, PCL, XPS, raster and vector files, plus ASCII text. It fits best when you need server-side, high-throughput document processing rather than interactive desktop editing.

What Ghostscript actually does

At its core, Ghostscript reads a page description language and produces output in another form. That single capability covers a lot of ground:

• Conversion between PDLs and document formats
• Compression and optimization of PDFs
• Native rendering to raster and conversion to vector formats
• Color management, imposition, and custom screening for print-quality output

Because it's written entirely in C, it runs on most operating systems and platforms, including Windows and macOS.

Common use cases

The site lists these scenarios where Ghostscript is typically deployed:

The Ghostscript product family

Ghostscript isn't a single binary—it's a set of interpreters built on the same graphics library:

• Ghostscript — the core PostScript and PDF interpreter.
• GhostPDF — the new PDF interpreter, written entirely in C, now enabled as the default and also available as a standalone, PDF-only binary.
• GhostPCL — an interpreter for PCL and PXL files.
• GhostXPS — an interpreter for XPS (XML Paper Specification) files.
• GhostPDL — the whole family bundled together, including all four elements.
• Ghostscript Office — a commercial version of GhostPDL that can also read and process common office documents such as Word, PowerPoint, and Excel.

E-invoicing with ZUGFeRD and Factur-X

Ghostscript can generate ZUGFeRD and Factur-X compliant e-invoices by embedding structured XML invoice data into PDF/A-3 documents. This supports standards-based, automated e-invoicing workflows—useful if your billing pipeline needs machine-readable invoice data inside a human-readable PDF.

How you integrate it

Ghostscript offers flexible integration: you can call it as a standalone command-line application, or integrate it directly into your application as an SDK. That choice usually comes down to whether you want a separate processing step or in-process document handling.

If your need is advanced PDF extraction rather than conversion, the site points to MuPDF, a fast, lightweight document-parsing solution compatible with Python, .NET, JavaScript, C#, and more.

When Ghostscript is the right fit

Choose Ghostscript when you need:

• High-throughput, server-side conversion or compression
• Standards-based archiving (PDF/A) or e-invoicing (ZUGFeRD/Factur-X)
• Print-production quality with color management and screening
• A C-based tool that runs across most platforms

It's less suited to interactive, desktop-style PDF editing—its strength is automated, pipeline-oriented document processing.