Frequently Asked Questions

Frequently Asked Questions (FAQ) about issues that have come up more frequently than others over the years with TCPDI, TCPDF, FPDI and FPDF use in PDF watermarking/passwording.

Why doesn’t the first page get stamped?

If PDF Ink is skipping the first page, maybe the parser (TCPDI or FPDI) is not reading that page as part of the document. Is it possible the cover page was added as an afterthought to an existing PDF? That’s called an incremented PDF. TCPDF struggles with some incremented PDFs.

Alternatively you can try to repair the PDF yourself. The cover page must be reintegrated into the PDF source code, and often this can be done by removing it, adding it back in, and saving the file as a PDF.

We recommend using a PDF viewer such as Apple Preview to delete the cover page, save, then drag and drop the cover page back into place from another open version of the same file, then ‘Export as PDF’ to save it. This should help smooth out any problematic PDF syntax issues. Unfortunately we know of no other PDF reader (Windows or Mac) that can help the way Preview does for syntactically-incorrect PDFs. If you know of one, please reach out.

Why does the stamp go off the page, create new blank pages, or change the box size?

Your content text string or image is too big or long for the page size! The PDF writer created a blank page trying to accommodate the overflowing text.

Try decreasing font size, adjusting margins smaller, adjusting rotation, or using the X and Y fine tuners to move the content back onto the page. The built-in adjustments on the settings page ultimately allow for stamping on all document sizes. If your PDF has pages of more than one size, you might want to measure from the bottom of the page instead of the top (using a negative value for the Y fine tuner). You may need to edit your content if it is too verbose.

Why does the PDF have extra white space (or other changes that aren’t intended)?

If you find the base PDF is different after it is manipulated, it’s quite possible the PDF reading library struggled with the PDF’s syntax (see “trouble PDFs“). Either upgrade your PDF library, or attempt to repair the PDF.

Try re-saving the file with Apple Preview, or editing crop boxes/clip paths with Adobe Acrobat/Illustrator, then try again. Bottom line: your PDF must have reasonably predictable PDF syntax in order for a machine to be able to read it consistently across all applications. Upgrading to SetaPDF-Stamper can solve these issues because not only does it attempt to repair poor syntax, but at default it does not read the entire PDF into memory.

There are countless variations and interpretations of PDF syntax such that the application you use to view your PDF might show it differently than the next application.

A white border is added

This is basically the same as “extra white space”, above. White border/margin added to top of page (or other area). This is most often caused by a layer in the PDF the original designer was either unaware of, or believed wouldn’t cause issues. It’s causing issues now. You can either try re-saving the PDF as described in the paragraph above, or opening the PDF with an editor such as Adobe Acrobat and finding/deleting the extraneous layer.

It’s also recommended to try a different library set. Unfortunately it’s possible one parser is just “seeing something that isn’t there.”

I only get a bunch of blank pages

If you are encrypting your PDF and are getting all blank pages, your server might not support the encryption level you’ve chosen. This happens more often with AES encryption, so try RC4 instead. OpenSSL must be enabled on your host/server.

I am getting an error message

Check out our list of error messages to see if yours is listed, and maybe get an answer right away!