You've exported 12 screens from Figma. The client doesn't use Figma. Emailing 12 PNGs creates 12 attachments to lose track of. Inviting them to a Figma file adds friction ("set up an account, here's how to comment").
A single PDF is what most non-design clients prefer.
Export from Figma to PDF
Figma exports frames to PDF natively — file > export > PDF. Each frame becomes a page. If you're working in another tool, convert images to PDF for image-only exports. The single-file format is what clients want.
Combine multiple flows
If the project has multiple flows (onboarding, checkout, settings), build each as its own PDF and merge PDF with section dividers. A clear contents page at the front ("Onboarding: pages 2-6, Checkout: pages 7-12") helps the client navigate without losing track.
Annotate for context
Use annotate PDF to add designer notes — what's intentional, what's a question for the client, what needs feedback. Context-on-the-page beats a long email thread. The client can annotate back using their PDF reader's comment tool, and the feedback loop becomes one document, not five emails.
Compress and send
Design mockups can be heavy. Compress PDF before sending. Test on a phone — design clients often review on mobile during commutes. If the compressed version still reads cleanly at phone size, you've compressed correctly.
FAQ
Should I send Figma links or PDF?
PDF for non-design clients. Figma links for clients who'll be actively collaborating with designers.
How do I include interactive prototypes?
PDFs can't show interaction. For prototypes, send the PDF for static review plus a separate link to the live prototype.
Can the client annotate the PDF directly?
Yes — Adobe Reader, Preview, and most PDF readers support adding comments. Their annotated PDF comes back as feedback.
What about Figma's Dev Mode handoff?
Dev Mode is for engineers, not non-design stakeholders. PDF for review, Dev Mode for build.
One PDF beats 12 image attachments. Combine your Figma exports in Flint and reviews go faster.