Private prepress structure audit

EPS / PostScript DSC Inspector & Bounding Box Validator

Open an EPS or PostScript file to audit its DSC header, integer and high-resolution bounds, pages, resources, nested blocks, trailer, and EOF—without uploading or executing the file.

Local source

Choose or paste EPS/PostScript

No local file selected.

Maximum 10 MiB. Plain PostScript and DOS EPS binary preview containers are read as bytes. No PostScript operators are run.

Choose a file or paste text to begin.

File bytes, PostScript text, comments, and measurements stay in this browser tab. The inspector never executes PostScript or uploads the source.

What DSC comments describe

Adobe Document Structuring Conventions use comments such as %%BoundingBox, %%Pages, %%Page, %%DocumentNeededResources, %%Trailer, and %%EOF to make PostScript easier for spoolers and document managers to inspect. EPSF adds a single-page exchange profile and requires a usable integer bounding box. %%HiResBoundingBox can preserve fractional-point geometry, while the integer box should enclose it.

How byte-counted data is handled

%%BeginBinary and byte-counted or line-counted %%BeginData sections are skipped according to their declared length. This prevents DSC-looking bytes inside image or font payloads from becoming false pages or trailers. The report checks matching end comments and also balances common document, resource, file, font, setup, and page-setup blocks.

Plain EPS and DOS EPS preview containers

Most EPS files begin directly with %!PS-Adobe. Older DOS EPS files can wrap the PostScript section with a 30-byte binary header and optional WMF or TIFF preview. The inspector validates declared segment boundaries and audits only the exact PostScript segment. Preview images are inventoried but not decoded, and a header checksum is reported only as stored metadata rather than treated as proof of integrity.

Preflight and security boundary

This is a DSC comment and container inspector, not a PostScript interpreter or complete preflight engine. It cannot prove that operators execute, fonts and resources exist, a file renders safely, the declared box encloses actual marks, colors and separations are correct, or output is suitable for a particular RIP. PostScript is executable code: do not run an untrusted file merely because its comments pass these checks. Use a maintained sandboxed interpreter and professional preflight workflow when rendering or production assurance is required.

Frequently asked questions

Does the file leave my computer?

No. File bytes are read by JavaScript in this browser tab. There is no upload endpoint.

Why can a valid-looking file still fail to print?

DSC comments describe structure; they do not validate the PostScript language program, external resources, device assumptions, or RIP behavior.

What does “(atend)” mean?

It tells a DSC-aware reader that the concrete value is supplied in the trailer. This inspector resolves supported header fields there and reports a missing trailer value as an error.

Can this repair an EPS?

No. Rewriting comments without interpreting the actual marks can create a misleading or unsafe file, so this tool is deliberately read-only.

Format reference: Adobe Technical Note 5001, PostScript Language Document Structuring Conventions Specification, version 3.0.

Inspect PDF page boxes · Check image print resolution · Browse printing tools