Figma Dev Mode Spec Prints Without Measurements — Which Export Settings Strip Them Out and How to Keep Every Value

Hey! When Figma Dev Mode spec prints are missing measurements, it’s usually not the design losing sizes — it’s the spec/inspect overlay not making it into the print/PDF path.

Before we touch anything, I want to pin down what you mean by “spec prints” because there are a few common workflows:

• Browser print (Ctrl/Cmd + P on a Dev Mode/Inspect view or a “ready for dev” view)
• Exporting frames to PDF (File → Export / selection export) and expecting measurement callouts to appear
• Using measurements/annotations in Dev Mode and then trying to “print” that as a spec sheet

Quick questions (no steps yet):
1) Are the measurements missing only in the printed output/PDF, or are they also missing on-screen in Dev Mode?
2) Are you in Figma web (Chrome/Edge) or the desktop app?
3) What’s your access level to the file (viewer, dev seat, full design seat), roughly?

Got it — that helps. If you can see measurements in Dev Mode on-screen but they disappear when printing, that points to a print/rendering limitation, not missing data.

There are a few usual suspects for “measurement overlay doesn’t print” in web apps like Figma:

• The measurement UI is an overlay (not part of the canvas), and browser print/PDF ignores it.
• You’re printing the wrong surface (e.g., the canvas exports, but the Inspect panel/measurement labels aren’t part of it).
• Seat/permission differences can change what’s available (measurements vs annotations vs inspect details).
• Focus view vs full UI: some views show specs differently, and printing behaves differently.

Let me ask it in a “symptoms first” way:
1) When you say “print specs,” are you using Ctrl+P from the browser, or exporting from Figma (Export PDF)?
2) Do you expect the PDF to show width/height labels on top of the design, or is it okay if the PDF is the design + the measurements listed in a side panel?
3) Are you measuring frame sizes, or spacing between layers (padding/margins), or both?

That expectation makes sense — but it also explains the mismatch. The spacing “distance” labels you see while inspecting are typically a temporary measurement overlay, not part of the exported canvas. When you print a web page, the browser usually captures the DOM content it thinks is “printable,” and overlays can get dropped or simplified.

Let’s keep this non-destructive and just confirm where the measurement data exists in your setup.

Safe checks (pure observation):
• Selection type: when you click a layer, do you see its W/H in the Inspect panel reliably, or does it sometimes show “—” or nothing?
• Auto Layout / constraints: is the spacing you need coming from Auto Layout padding/gap, or manual positioning? (Because Dev Mode displays those differently.)
• Units: are you expecting pixels, or are you looking for rem/pt/mm? (Sometimes a “missing measurements” report is actually “units not matching what we expect.”)

Also: do you know if this file uses variables/tokens or multiple modes? That can change what the Inspect panel emphasizes.

Perfect — that narrows it to a “shareable spec artifact” problem, not an “inspect is broken” problem.

Here are the most common reasons a Dev Mode spec print ends up missing measurement labels, even when Dev Mode itself works:

1) Browser print vs canvas export mismatch
Ctrl+P produces a printed snapshot of the page layout. Measurement labels that appear only during interaction (hover/hold-to-measure) often won’t be included.

2) Inspect panel vs overlay expectation
Dev Mode can show sizes, padding, and gaps in the Inspect panel, but that data isn’t automatically “burned into” a PDF when you print the page.

3) View mode differences
Some people print from a “focus view” or a shared link, and the UI changes enough that measurements don’t appear the same way.

To diagnose cleanly, tell me this (still no changes):
• When you generate the PDF with Ctrl+P, does the PDF include the right sidebar (Inspect panel), or only the canvas area?
• When you click a layer and see W/H, is the Inspect panel docked and visible, or do you need to expand it each time?
• Are you printing from inside a shared link, or from the normal file UI?

That’s consistent with how browser printing treats complex web UIs: it’s often optimized for documents, not interactive inspector layouts.

Since your goal is “a PDF that includes measurements,” we can treat this as a requirements/constraints check and avoid breaking anything in the file.

A few “root-cause” checks that are safe and help a lot when escalating internally (or when comparing web vs desktop):

• App surface: does the same thing happen in Edge (Chromium) or the Figma desktop app, or only Chrome? (This tells us if it’s browser-print CSS/renderer specific.)
• Zoom + display scaling: are you at 100% browser zoom and normal Windows display scaling, or is it 125%/150%? (Sometimes print capture crops panels when scaling is non-default.)
• Selection context: are you selecting the frame or layers inside it? Some “missing measurements” reports are actually “I’m selecting instances inside components and the panel shows less.”
• Seat + permission: in some workspaces, measure/annotation capabilities vary by seat type and file permission — which changes what you can display and share.

If you can answer just one: is your Windows display scaling anything other than 100%?

125% is a useful clue — it doesn’t “cause” Dev Mode to fail, but it can absolutely change how print output crops side panels or scales UI overlays. That can make it look like measurements are missing when they’re simply not being captured in the print layout.

Here’s the safe way to document this without changing any file settings or component definitions:

1) Capture what’s visible on-screen
• In Dev Mode, select one example component and note what you see in the Inspect panel (W/H, padding, gap, typography).

2) Capture what gets printed
• Run Ctrl+P → Save as PDF and note whether the output contains the canvas only, or canvas + panel, and whether anything is cut off.

3) Compare environment
• Browser (Chrome) + OS scaling (125%) + whether you’re in a multi-monitor setup (different scaling per monitor can matter).

And one “expectations” check: the hover/hold-to-measure overlays (distance labels) are often interaction-only. Even if we fix the print cropping, those overlays may not be designed to print as a spec sheet.

Do you need the PDF to show measurements overlaid on the canvas, or would a “spec summary” (values visible in a panel/annotation list) meet the requirement?

Totally fair — and you’re describing the key distinction: Dev Mode is built for interactive inspection, while “printable specs” are a different deliverable. So the goal here is to determine whether you’re dealing with:

• A print capture problem (side panel cropping/scaling, browser print behavior, OS scaling), or
• A visibility/access problem (seat type / permission limits affecting measure/annotation tools), or
• A workflow mismatch (expecting interactive measurement overlays to export/print like markup).

If you want a clean, support-ready bundle to hand to your team (or to compare web vs desktop), capture these exact items:

Environment
• Windows version + display scaling (125%) + browser (Chrome version).

File & access
• Workspace plan/seat (Dev seat) and your permission level on the file (view vs edit).

Where measurements appear
• On-screen: which measurements you can see (W/H, Auto Layout padding/gap, spacing hints).
• Print/PDF: what disappears (overlay labels, inspect panel, both).

Repro steps
• “In Dev Mode, select layer X → see W/H. Press Ctrl+P → Save as PDF → sidebar cropped / no measurement overlay.”

With that, you can decide whether you need a different shareable artifact (like annotations) or whether the issue is primarily the print renderer/UI capture. No risky changes required to get to that decision.