Digital vs Visual PDF Signatures vs Professional Seals

Choose based on what the recipient must verify. A visual appearance may satisfy a presentation requirement. To detect whether protected bytes changed, use a certificate-backed signature. When a professional seal is required, review its artwork under the applicable board’s rules, then sign separately if cryptographic integrity is also required.

This guide explains product behavior, not whether a mark satisfies a contract, statute, licensing board, or court. Confirm those requirements with the responsible authority.

PolyPDF uses a Digital ID to create a CMS signature over defined PDF byte ranges. A verifier recalculates the digest and compares it with the signed data. If the bytes no longer match, integrity fails. This differs from inspecting a checkmark or signer name drawn on the page.

Integrity and trust are separate questions. The identity in this example is self-signed, so it reads as Trusted only on a computer that has been configured to trust it. That is not public certificate-authority trust and not an endorsement of the signer. A recipient’s decision can depend on its own trust anchors, certificate chain, policy, signing authority, signing time, and revocation information.

Visual mode can place a saved signature, a standard style, or a drawn mark, and the current release lets you choose its color. The placement is one undoable edit. That may suit an internal approval or a process where another system records identity and consent. It does not create a CMS signature and cannot tell a later viewer whether page bytes changed.

• Do not describe a visual mark as digitally signed merely because it looks like handwriting or includes a date.
• A visual mark records what the page looked like. It does not record who applied it, or whether the bytes changed afterward.
• If integrity matters, pair the final visual layout with a certificate-backed signing step or the organization’s approved signing platform.
• Legal effect depends on context and governing rules; cryptographic capability alone does not decide enforceability.

Professional Seal Maker asks for a profession, jurisdiction, and the fields your seal needs, then places the finished seal on the page as an image-stamp annotation. The seal is graphic artwork: it carries no cryptographic signature, and PolyPDF does not verify license status or board compliance. Deciding that a document may be sealed, and standing behind that decision, remains the licensed professional’s own responsibility.

• Compare spelling, license number, profession, jurisdiction, and any dates against the professional’s authoritative records.
• Check current licensing-board rules for appearance, size, wording, electronic sealing, responsible control, and permitted documents.
• Keep the seal editable while drafting, then finish all page-content changes before certificate signing.
• Signing afterwards is a separate step. A certificate signature protects the finished bytes; it does not make the seal itself correct, current, or permitted.

A seal graphic can be visually accurate and still be used improperly. The licensed professional whose identity appears on it is responsible for the decision to apply and issue it.

1. Start with an authorized unsigned working copy and complete revisions, markups, page operations, headers, watermarks, and sanitation first.
2. Generate the seal artwork, compare every field and its appearance with the applicable board requirements, and place it on the page.
3. Have the responsible professional review the entire final document, not only the seal area.
4. Open the Signatures panel, import or select the professional’s approved Digital ID, then use Apply Signature in certificate mode and place the signature appearance.
5. Save the signed output under the issue filename, close it, reopen it, and inspect the Signatures panel for the integrity result and certificate details.
6. Send the exact saved file without further page-content edits. Ask the recipient to validate it in their own PDF viewer and under their trust policy.

This sequence keeps the roles clear: the seal communicates a professional designation, the professional supports the issue decision, and the certificate signature protects signed byte ranges. None substitutes for another.

Valid With Changes is not the same claim as Valid and unchanged. In the example above, the signed revision’s Byte Range, CMS Digest, and CMS Signature are valid. The document later received an incremental update allowed by its DocMDP level 3 policy, so the panel says Modified After Signing: Yes and Covers Document: No. Those exact fields—not a green icon by itself—define what was checked.

If a future result instead reports an invalid byte range, CMS digest, or CMS signature, the cryptographically checked content did not pass that test. Do not cover the warning or replace the appearance. Return to the authorized source, determine whether the change was expected, complete the new issue, and sign again with the proper identity.

• Finish content editing before signing. Some certified signatures allow limited later actions, but page-content changes may be blocked or invalidate the signature.
• Verify the reopened saved file, not only the document still open after signing.
• Review integrity, certificate trust, revision coverage, permissions, timestamp, LTV, and revocation fields separately; one passing field does not supply what another one is missing.
• A self-signed identity is trusted only where someone has installed it. Recipients evaluate it under their own trust policy.
• Preserve the signed original. Do not use a print-to-PDF or image export as a replacement when verifiable signature data must survive.