Why Your Signature Disappears When Someone Else Opens the PDF

Drop your document here and sign it now. PDF, Word and Excel all work: a .docx or .xlsx is laid out in your browser exactly as it was written, so there is nothing to convert first. Add a signature, a date, a company stamp or a watermark, then download it sealed. Free to start, no account, and the file is never uploaded to do it.

You signed the contract, you can see your signature on the page, and the reply comes back: "there is nothing there". Nothing you do on your machine reproduces it, because on your machine it looks fine. This is one of the most unnerving things that happens with a signed PDF, and it happens constantly. The cause is not corruption and it is not the other person doing something wrong. It is which layer of the file your signature was written to.

A PDF has more than one place to put a signature

The page content is the part every reader draws. Below that there is an annotation layer, which holds comments, form fields, stamps and, in many tools, the signature appearance. Annotations are optional to render, and viewers disagree about which ones to draw. Acrobat draws all of them. Apple Preview, Chrome’s built-in viewer, some Android readers and a good many document management systems draw fewer, and a signature that lives only in an annotation can vanish in any of them.

This is why the problem looks so random. It is not random at all: it depends entirely on what opened the file. Acrobat to Acrobat, everything is fine. Acrobat to Preview, or Acrobat to whatever the bank’s intake system uses, and the page comes up blank where your name should be.

The three ways this shows up

The signature is invisible in one viewer and fine in another. Classic annotation problem. The file is not damaged, it is being drawn selectively.

The signature prints but does not appear on screen, or the reverse. Same cause, different renderer: the print path and the screen path in some applications treat annotations differently.

The signature appears with a bar across the top saying validity is unknown, or that the document has been altered since signing. That is a different thing entirely, a certificate-based digital signature whose certificate chain the reader cannot check. The signature is there, the reader is telling you it cannot vouch for it.

How to know which one you have, in about ten seconds

Open the file in a plain viewer that draws little: Chrome, or Preview on a Mac. If the signature is missing there and present in Acrobat, it is in the annotation layer. Then try selecting the text around it and copying: if a signature can be dragged, selected as an object or deleted with a key press, it was never part of the page.

That last test is the one worth doing before you send anything important, because a signature that can be deleted with a key press can also be moved onto a different document by anybody who receives it.

The fix: flatten it, then seal it

Flattening writes the signature into the page content itself, where there is no layer to skip and no object to drag off. Every viewer on earth draws page content, so a flattened signature renders in Preview, in Chrome, on a phone, and in the document system at the far end that nobody has ever heard of.

Sealing goes one step further and fingerprints the finished file, so if a single byte changes afterwards it is detectable. Flattening makes the signature visible everywhere; sealing makes it provable. You want both, and doing them in one pass takes about a minute.

Drop the document into the box at the top of this page, place the signature, and download it. What comes out is flattened and sealed, with a QR code the recipient can scan to confirm they are looking at the document you sent rather than a copy of it.

What to send the person who cannot see it

If a signed document has already gone out and come back as "blank", do not argue about their software. Re-send a flattened copy, and say one sentence: "here is a flattened version, it will render in any viewer". You will not have the conversation twice, and you will look like somebody who knows what they are doing rather than somebody blaming a PDF reader.

If they need to check that the document is genuine rather than just visible, send them the verification link as well. Scanning the code on the page tells them the file has not been changed since it was signed, which is a stronger answer than "it looks right on my screen".

Why this keeps happening

Because the annotation layer is the easy place to put a signature and the fastest to implement, and because it looks correct to the person who signed. The failure only shows up on somebody else’s machine, after the document has left, which is the worst possible time to find out.

The habit worth building is simple: before a signed document goes anywhere that matters, open it in a viewer other than the one you signed in. Ten seconds, and it catches this every time.

Questions people ask about this

Why is my signature not showing in a PDF?

Because it was written to the annotation layer rather than into the page. Acrobat draws annotations, and Apple Preview, Chrome's built-in viewer and many document systems draw fewer of them, so the same signed PDF looks fine on your screen and blank on theirs. Flattening writes the signature into the page content, where every viewer draws it.

How do I sign a PDF so it shows everywhere?

Sign it and seal it rather than placing an image on it. A sealed document has the signature as part of the page and a SHA-256 fingerprint over the whole file, so it renders in any viewer and any later change to it is detectable.

Can I sign a Word document or an Excel spreadsheet the same way?

Yes. Drop the .docx or .xlsx in and it is laid out in your browser exactly as Word or Excel would lay it out, then signed. There is nothing to convert first, and no copy of Office is needed.

Is a PDF signature legally binding if it does not display?

The display is not what makes it binding, but it is what makes it useful. Intent, identity and integrity are what the ESIGN Act, UETA and eIDAS look at. A signature the recipient cannot see is a practical failure long before it is a legal one, and it is the reason documents come back refused.

Make a signature free →

What PDF Verified is, and what it is not

Electronic signature law is settled in broad terms and specific in the details. The ESIGN Act, UETA, eIDAS and their equivalents recognise electronic signatures across more than 190 countries, and what decides a particular case is intent to sign plus evidence connecting the signature to the signer, which is what the audit certificate records. Certain document types carry their own formalities wherever you are: deeds, wills, some property instruments, and anything requiring a witness or a notary. Sign only what you are authorised to sign, since applying another person signature without their authority is forgery whatever tool is used.

PDF Verified is a tool for preparing, signing, stamping and checking documents. It is not a law firm, a compliance service or a forensic examiner, and nothing here is legal, financial or compliance advice. Requirements differ by country, by document type and by the party asking, so check what applies to your document before you rely on it, and take advice where the document matters. You are responsible for the documents you create, sign and send, and for having the authority to do so: signing or stamping in somebody else name, or as an organisation you do not represent, is forgery whatever tool is used. To the extent the law allows, we accept no liability for how a document made with this tool is used or relied on. The full position is in our terms of service.

More on esignatures & signing

Tools