Design Handoff in Figma for an Imported Web Page

Hand an imported web page to a developer in Figma: clean the file, mark sections ready for dev, share the import report, and annotate the gaps.

TUTORIALDEVELOPERPublished

Introduction

A design handoff in Figma for an imported page works when the developer can tell what is deliberate and what is leftover from the import. Clean the file, group the finished work into sections, mark those sections ready for dev, and pass along the import report. Then add notes for anything the layers cannot hold.

An imported page is an odd handoff. The developer may have written the original page, or may be seeing it for the first time. Either way, they open a file full of layers that came from CSS, and they need to know which parts to rebuild, which to keep, and which to check in a browser. The steps below cut most of the back and forth.

Clean the file before anyone else opens it

Start with the noise. An import carries wrapper frames, hidden elements and layers you will never edit. Delete what has no job, and flatten only what you will not touch again. We cover that order in detail when we clean up the import first.

Then follow Figma's own advice for handoff-ready files. According to the Figma help center, you should:

  • Name pages descriptively so others can see what is ready for development.
  • Give styles relevant and descriptive names.
  • Create a single page with instances of all your components, so collaborators check one place.
  • Apply export settings to the frames, components and assets a developer may need to export.

Pick names a developer would use in code. "Hero", "Pricing card" and "Footer links" beat "Frame 1042". Developers rely on layer names when they inspect a design. Rename any imported layer that makes no sense outside the original page.

One more setup choice: who gets what access. Figma says that inviting a collaborator with can view access is enough in most situations. View access lets people select layers, read properties in the Inspect panel, copy text, measure distances and comment. If you let view-only users copy and share the file contents, they will not be able to explore or export assets, so decide that before you send the link.

Mark sections ready for dev

Why sections matter

Group finished work into sections. In Dev Mode, Figma prioritizes content that sits inside a section. Content outside a section is still visible in the left sidebar, but it is collapsed by default. If your imported page sits loose on the canvas next to old experiments, the developer has to guess which frame counts.

Put each page or flow that is final in its own section, and name the section for the thing it shows: "Home, desktop" or "Pricing, desktop". Leave scratch work outside.

Statuses, seats and plans

Select a section, frame or component in Dev Mode and click Mark as ready for dev in the toolbar. Figma's ready for dev view then lists every design with a status in one place, with a counter, filters for All, Ready and Completed, and sorting by recent activity, pages or name.

The part that matters most for an imported page is change tracking. The view highlights when a design was most recently updated, so a developer can tell whether it changed after the first handoff. If you fix a font or restructure a frame after marking it, the developer sees it.

Check plans and seats before you promise any of this. As of November 2026, Figma's Dev Mode guide lists Dev Mode on the Professional, Education, Organization, Government and Enterprise plans. The ready for dev status comes with every plan that has Dev Mode. The Completed status is only for Organization and Enterprise. Changing a status needs a Full or Dev seat.

Hand over the import report with the file

Most people skip this step. It prevents the most confusion. An imported page is a faithful, editable copy of the structure and styling, but it is not a pixel-exact clone. Some things fall back, and the developer should hear about them from you, not find them by accident.

UnHTML writes an import report after each run. It lists every font that was substituted, every frame that reverted to absolute positioning, and every image that was skipped. Each of those is a place where the Figma file can differ from the live page. Fonts that are not installed are replaced (Inter is the default, and you can change it). We explain how missing fonts get replaced and logged in a separate article.

Turn each line of the report into one short note for the developer:

  1. Substituted fonts: name the font the live page uses, so they use the real one in code.
  2. Frames reverted to absolute positioning: say these were not translated to auto layout, and that the live page's CSS is the reference for how they behave.
  3. Skipped images: point to the original asset or the live URL.

Paste those notes into the file or the handoff message. Three lines about known gaps make the rest of the file easier to trust.

Name what the developer will reuse

Developers build components and tokens, so give them the shapes they will build. Repeated blocks such as cards, nav items and buttons should become components. If you are not sure how, read about how to turn repeated blocks into components, and about building a design system from an imported site if the file needs a wider set of tokens.

Two details help in Dev Mode:

  • Styles and variables applied to a layer show up in the inspect panel, so a layer that uses a named color style tells the developer the name, not only the hex value.
  • Export settings control what developers can download. Figma supports PNG, JPG, SVG and PDF, and Dev Mode can detect icons automatically and offer them as downloadable assets.

The inspect panel can show properties as code or as a list of values. The developer can click a value in the list to copy it. That makes consistent naming worth the time: a value with a name next to it is easier to use than one without.

Annotate what the layers cannot say

Layers describe a static frame. They do not describe behavior. Figma annotations let designers add context, specs and measurements directly on the design, so important properties are hard to miss. Use them for the things an import cannot capture:

  • Hover, focus and active states that the page only shows on interaction.
  • How the layout should respond between breakpoints, since one import is one viewport.
  • Anything you changed on purpose, such as a new headline or a swapped color.

Keep the annotations short and put them on the layer they describe. If something is only true of the original page and you are not changing it, say "match the live page" and link it.

Conclusion

Handing off an imported page comes down to four moves: clean the file, mark finished sections ready for dev, share the import report as a list of known gaps, and annotate behavior. Do those, and the developer opens a file that says where to trust the layers and where to check the browser.

Frequently Asked Questions

Does a developer need a paid Figma seat to see an imported page?

Not to look. Figma says view access lets people select layers, read the Inspect panel, measure distances and comment. Dev Mode itself needs a Professional or higher plan, and the ready for dev view depends on seat type, so check your plan before promising it.

What should the import report tell a developer?

It lists substituted fonts, frames that reverted to absolute positioning and skipped images. Those are the places where the Figma file differs from the live page, so the developer should check them against the browser.

Should I hand over the Figma file instead of the original page?

Hand over both. The Figma file shows the design decisions, and the original page remains the reference for behavior the layers cannot hold.

Questions

Does a developer need a paid Figma seat to see an imported page?
Not to look. Figma says view access lets people select layers, read the Inspect panel, measure distances and comment. Dev Mode itself needs a Professional or higher plan, and the ready for dev view depends on seat type, so check your plan before promising it.
What should the import report tell a developer?
It lists substituted fonts, frames that reverted to absolute positioning and skipped images. Those are the places where the Figma file differs from the live page, so the developer should check them against the browser.
Should I hand over the Figma file instead of the original page?
Hand over both. The Figma file shows the design decisions, and the original page remains the reference for behavior the layers cannot hold.