What do PostScript errors look like?

A PostScript error has two parts: the error and the offending command. Take a look at a typical PostScript error:

    %%[Error: limitcheck; Offending command: image ]%%

The error tells you exactly what problem the RIP encountered while processing your file. In the example, it is a limitcheck. Thankfully, there are a limited number of errors that can occur on PostScript devices. The offending command signals what specific PostScript command was being processed by the RIP when the error occurred. In some cases, the offending command doesn’t really look like a command but a series of random characters. This means the RIP has encountered some information in your printfile that it considers to be a PostScript operator but is not. This can happen with corrupted images, bad network connections and so on.

Can PostScript errors be solved?

Errors caused by bugs in applications or drivers are sometimes well documented and easy to resolve. The same is true for errors caused by limitations or bugs in the software of the RIP itself. Errors caused by corrupted data can be tricky to troubleshoot. The same is true for PostScript errors caused by incompatibilities between different applications and RIPs. If you do come across a PostScript error, and want to find a way around it, click here. This page will give you the information you need to resolve most issues. If you have an error that does not appear on this page, please send it to This e-mail address is being protected from spam bots, you need JavaScript enabled to view it . We will be glad to help