Sign a PDF on Mac: Preview or e-signature?

Mac Preview makes it pleasantly easy to put a signature image on a PDF. That is useful, but it is not the same job as collecting a signature from another person. The distinction matters when the document is a contract rather than a school permission slip.

The short answer

Use Preview on a Mac when you are adding your own mark to a low-risk document you control. Use an e-signature service when a second party must sign, when you need fields and reminders, or when you need evidence of the signing event. Both avoid printing, but they create different records.

Before you start

Decide first whether the PDF is an internal file or a bilateral agreement. Preview is quick for a personal form, but it does not turn a shared PDF into a managed signing process. For a contract, finalise the text, convert it to PDF, identify every signer and add the fields before any link is sent. Do not make substantive edits after the first signature.

The practical rule is to separate the document from the evidence about the document. A visible name or squiggle is useful to a reader, but it is not the whole record. For an agreement that matters, keep the final PDF, the completed event log, the invitation address and the version that was sent. That small bit of housekeeping is much easier than rebuilding a timeline after a disagreement.

A reliable way to do it

In Preview, open the PDF, show the Markup toolbar, choose the Signature button and create a signature using the trackpad, camera or iPhone. Place it, then save a separate completed copy. For an agreement, upload the same final PDF to InkRobin instead, place signature and date fields, and send the recipient-specific link. The platform records the completion events and produces the final version for both parties.

• Use the final version of the document, not a draft with unresolved comments.
• Put signature, date and any required text fields beside the relevant clause.
• Send the link to the person whose email address you have already checked.
• Ask the signer to review the whole document before they complete the signature field.
• Save the completed PDF and its audit record together in the same matter or client folder.

That sequence is deliberately boring. Boring is good here. It makes it clear which version was offered, gives both sides the same finished copy and avoids the familiar mess of several attachments called ‘final final’. It also makes the process workable on a phone: the signer needs a browser and a clear link, not a new account or an app download.

What the options look like

A realistic example

A solo architect needs to sign a supplier’s routine delivery acknowledgement and uses Preview because the supplier has asked only for a returned PDF. Later, the architect sends a consultancy agreement to a client. This time there are two parties, a fee, a start date and a cancellation clause, so a visible signature image is not enough. The agreement goes through a signing flow that captures when each person viewed and signed the same file.

The useful measure is not how polished the process appears in a demo. It is whether a busy person can complete it without a call, a printer or a password reset. A straightforward signing flow removes the tiny reasons people put a document aside. It also leaves the sender with evidence that is readable by a human, not locked in a proprietary dashboard.

The mistakes worth avoiding

The seductive mistake is to assume that a signature created through a polished native app carries more proof than it does. Preview can make a tidy PDF; it does not independently establish who controlled the computer, which version was received or whether a counterparty accepted the terms. Another mistake is overwriting the unsigned original. Keep that original and label the completed copy clearly.

Do not treat this as legal advice for a particular transaction. Some documents have special form, witnessing, identity or jurisdictional requirements. In the US, ESIGN and UETA make electronic records and signatures generally valid, but they do not erase statutory exceptions. In Europe and the UK, a simple electronic signature can be valid, while a regulated use case may need a different assurance level. Check the document type before promising a counterparty that any method will do.

A contract may not be denied legal effect solely because an electronic signature was used in its formation. — ESIGN Act, 15 U.S.C. §7001

How to make the right call

Choose Preview for personal annotation and an e-signature workflow for agreements that you may need to explain later. The issue is not whether one signature looks more ‘real’. It is whether your process shows consent, connects the signer to the record and protects the final document from quiet changes.

A good default is proportionate evidence. For an internal acknowledgement, a clear email and a saved PDF may be enough. For a client agreement, lease or confidentiality document, use a signing flow that records the email address, timestamps, IP address, user agent and a tamper-evident document hash. None of that makes a bad contract good; it does make a valid agreement easier to evidence.

Make the record useful next year

Once the document is complete, give it a name a colleague can understand without opening it. Include the party, document type and completion date, then store the signed PDF and certificate together with sensible access controls. Record where the unsigned source lives, but do not edit the completed copy. This is a small operational discipline, yet it is the difference between a settled record and a frantic search through old email when a renewal, invoice or dispute appears months later.

It is also worth telling the other party where their copy will arrive. People are more comfortable signing when they know they will be able to retrieve the final agreement afterwards. If an email is bounced, a signer says the details are wrong or a clause is under discussion, pause rather than trying to patch the live request. Void it, resolve the issue and send one clean final version. That preserves a record both sides can trust.

Finally, treat the signing request as part of the customer experience. Use the name people know you by, a specific subject line and a short explanation of why the document is arriving now. Check the request on both a laptop and a phone before a large send. If a recipient has accessibility needs, provide a workable alternative and make the document available in a form they can retain. Clear communication is not decorative: it helps establish informed action and stops a genuine request being mistaken for a phishing email.

Next step

If you have a PDF ready, try the workflow with one low-risk document first. Upload it, place the fields and send yourself a test link. You will see where the recipient hesitates before you ask a real customer, tenant or supplier to sign. InkRobin’s free plan covers five documents a month, so there is room to test the practical bits before changing a team process.