How to markup a Figma export for client review
To markup a Figma export, export the frame as a PNG or PDF, then either annotate it yourself using Preview on Mac or Figma's paste-in-place method, or share it through a browser-based review link your client can click directly — no Figma account, no file back-and-forth. The export route is the right call when your client isn't in Figma, because Figma's built-in commenting requires an account most clients won't create.
Export the frame as PNG or PDF
In Figma, select the frame you want to share. Open the Design panel on the right, scroll to Export, click +, choose PNG (for a single screen) or PDF (for multi-page flows), and hit Export. For pixel-perfect exports, set the scale to 2x before downloading — 1x exports often look soft on client screens. One thing most designers miss: Figma's built-in annotation layer (Shift T) does not export with the frame. If you need your redline callouts in the exported file, you have to either merge annotation frames into the design layer, or annotate after export.
Annotate the export yourself (before sending)
This is the markup-for-your-client approach: you mark up what you want reviewed, they approve or respond. On Mac, open the exported PNG in Preview, press Shift ⌘ A to open the Markup Toolbar, and use callout bubbles, arrows, and text labels to flag each element. Your annotations bake into the file — send it as-is. On Windows, open the PNG in Edge and use the Draw tool. In both cases, prefer callout arrows with text labels over freehand circles: a circle doesn't tell the client whether you mean the button or the padding around it. The limit of this method: you're doing all the markup. If you want the client to annotate — to tell you what they want changed — they have to mark up your marked-up file, and the round-trip degrades fast.
Share a Figma view link (when the client has an account)
If your client has a Figma account, set the share permission to 'Anyone with the link can comment' and send the link. They open the file in Figma, press C to activate comments, click the element, and type. You'll see their note in the Comments panel with a resolve button. This works well when the client is a product manager or designer who already uses Figma day-to-day. It breaks down with everyone else: 'it's asking me to sign up' is the response you'll hear from most clients outside the design and engineering bubble.
Share a browser-based review link (no account required)
The method that actually works for clients who aren't in Figma: export the frame, upload it to a review tool, and share the link. Your client opens it in any browser — on their phone, their work laptop, wherever they are — clicks the element they mean, and pins a note right to it. No account. No downloaded file to re-annotate and email back. The note arrives anchored to the pixel they clicked, not buried in a paragraph describing the area near the top. This is the right approach for client approvals, non-technical stakeholders, or any situation where you can't control what's installed on their device.
If you want your client to do the markup — not just view it — skip the export-and-email loop. Drop the exported PNG or PDF into Drafty and share the link. They click the exact element they mean and pin a note in their browser, no Figma account needed. You reply in the thread, push a revised export to the same URL, and resolve each note when the change is done. The full round-trip stays in one place instead of three email chains and an annotated screenshot someone called 'FINAL_v2_USE_THIS.png'.
Open a live demoQuestions
- Do Figma annotations export with the PNG?
- No. Figma's built-in annotation layer (Shift T) is only visible inside Figma — it does not render in exported PNGs or PDFs. If you need callout notes in the exported file, you have to manually build them as regular design layers (text boxes + arrow lines on a dedicated annotations frame) before exporting.
- Can my client markup a Figma export without a Figma account?
- Not through Figma itself — commenting requires an account. The workaround is to share the export through a link-based review tool. Your client opens the link in any browser, clicks the element they want to flag, and leaves a note pinned right to it. No account, no app install.
- What is the best format to export from Figma for client markup?
- PNG at 2x for single screens — it's sharp, universally viewable, and easy to paste into any review tool. PDF for multi-screen flows when you want one file rather than many images. Avoid SVG for client review (browsers handle it inconsistently) and avoid exporting at 1x (looks soft on retina screens).
- How do I collect feedback on a Figma export without sharing the whole Figma file?
- Export the frame you want reviewed and share only the export — not the Figma file link. This keeps layer names, internal comments, and work-in-progress frames hidden. A review link on the exported image gives the client exactly the surface they need to comment on, with nothing else exposed.
- How do I keep track of which markup feedback has been addressed?
- Email threads and re-annotated PNGs have no resolution state — there's no way to mark a note 'done' without hunting back through the chain. A thread-based review link lets you resolve each note when you push the fix, so both you and the client see at a glance what's been addressed and what's still open.
- What is the difference between marking up a Figma export and sharing a Figma prototype?
- A Figma prototype share shows the live interactive file — the client can navigate between frames but needs to create a Figma account to leave comments. A Figma export is a flat PNG or PDF of one or more frames — a static snapshot. Marking up the export is the right move when the client isn't in Figma, when you want to share a specific version without exposing the work-in-progress file, or when you need the annotated artifact as a deliverable.
Keep exploring
Stop emailing files back and forth.
Share one link. They comment on the exact spot — no account, always the current version.