Importing a Shopify Storefront Into Figma for a Redesign

Save each key Shopify page as a self-contained file, drop it into the plugin, then check the report. Here is how sections become frames and what to verify.

TUTORIALDESIGNERPublished

To get a Shopify storefront into Figma, save each page you care about as a self-contained HTML file (or a Safari web archive), drop it on the plugin, and read the import report. A Shopify page is a stack of theme sections, so the result is a column of frames you can rename and edit. Expect substituted fonts and a few absolute-position fallbacks, not a pixel-exact clone.

This tutorial assumes you have Figma, the UnHTML plugin, and either admin access to the store or a preview link from someone who does. It covers how a theme page is built, how to get past a password page, how to capture, and what to check afterward.

How a Shopify storefront is put together

A Shopify theme is a fixed set of directories: assets, blocks, config, layout, locales, sections, snippets and templates. According to Shopify's theme architecture docs, the layout folder holds Liquid files that wrap each page, and a theme.liquid file must exist there. That wrapper carries the repeated pieces, including the header and footer section groups.

Templates decide what appears on each page type. JSON templates "act only as a wrapper for sections," while Liquid templates contain code. Sections are the reusable, merchant-editable modules, and blocks are smaller pieces merchants can add, remove and reorder inside a section.

There is a ceiling worth knowing. JSON templates and section groups can render up to 25 sections, and each section can have up to 50 blocks. A long home page is therefore a bounded stack, not an open-ended one.

For an import, the point is that you capture the rendered page, not the theme files. Each section arrives as a wrapper with its content inside, which maps naturally to one top-level frame per section. The header and footer repeat on every page, so you only need to clean them up once.

Pick the pages that carry the redesign

Don't import the whole store. Pick one page per template type, plus one content page:

  1. The home page.
  2. One collection page.
  3. One product page, ideally one with variants and a long description.
  4. The cart page.
  5. One content page, such as About or a policy page.

That set shows you every distinct layout the theme uses. Write down the date you captured each page and the theme version if the admin shows one, because a merchant can edit sections at any time and your Figma file will otherwise drift from the live store without anyone noticing. A short note on the Figma page, such as "captured 2026-11-05 from the live theme", is enough for the next person who opens it. Product pages that differ only by photo and price add layers without adding information. The same page-selection logic applies to importing a WordPress theme page for a redesign.

Get past private mode before you capture

A store in private mode hides from visitors and search engines. Per Shopify's preferences docs, "when private mode is active, a landing page with a password option and a custom message is displayed to your visitors." If you save the store URL while that page is showing, you capture the password page and nothing else.

You have two clean ways around it:

  1. Open the store with the password. Enter the storefront password in your own browser, then save the page from that session. This is the same idea as capturing a page behind a login.
  2. Use a theme preview. In the admin, open Online Store, then the actions menu next to the draft theme, and click Preview. The Shopify Help Center says the link button in the preview bar copies a shareable link, and the theme does not need to be published.

Mind the expiry. Visitor previews do not require authentication and expire 2 days after the URL is created. Merchant previews require admin authentication, have access to checkouts, and expire 30 days after creation. The URL in your address bar after you click Preview is a merchant preview.

Shopify's docs don't say how a visitor preview behaves while private mode is on, so test the link in a private browser window before you rely on it.

Capture the page

Once the real storefront is on screen, you have three ways to get it into the plugin:

  • Self-contained HTML. Save the page as a single file so styles, images and fonts travel with it. See exporting self-contained HTML from Chrome.
  • Safari web archive. The plugin accepts a .webarchive the same way. See saving a page as a Safari web archive.
  • scene.json from the CLI. For a live URL, the open-source capture CLI runs a headless browser and writes a scene file you drop into the plugin. A store behind a password page is easier to save from your own browser than to script.

Then drop the file on the plugin. By default the import makes no network requests, so assets that the saved file does not contain will not be fetched. What to check before you import covers the opt-in for remote fetching.

The free plugin caps an import at 500 layers. A home page with many product cards and a mega menu can pass that. As of November 2026, Pro costs $39 one-time per editor and removes the cap. Compare against the unhtml.pro pricing before you decide, since launch pricing may change.

Check the import

Open the import report first. It lists every substituted font (Inter by default), every frame that reverted to absolute positioning, and every image that was skipped. Shopify themes often load brand fonts from a font service. If those fonts are not installed on your machine, expect the swap.

Then walk the page from top to bottom, one section at a time:

  • Fonts. Install the real brand fonts and swap them in, or accept the substitute for a rough comparison.
  • Auto layout. Where the page used flex or grid, the plugin maps spacing, padding, wrap and stretch to auto layout. Where it cannot reproduce the geometry, the frame falls back to absolute positioning.
  • App-added sections. Reviews widgets, popups, announcement bars and chat buttons are often injected by scripts. A static file may show them partly or not at all. Treat anything missing as a note for the redesign, not as a defect in the import.
  • Images. Check for skipped images and replace them from the store's media library.
  • Responsive width. If the redesign needs the mobile layout too, check how the viewports came through in the import and compare them with the live store on a phone, then note any section that looks different at each width.

Figma's own auto layout is built to mirror CSS. In its guide to auto layout with CSS flexbox in mind, Figma notes that padding takes priority over a frame's set width, matching a border-box element, and that inside strokes count toward layout like CSS borders. So a bordered card can sit a few pixels off in Figma until you check its stroke setting.

Turn the import into a redesign baseline

Keep the untouched import on its own page and duplicate it before you edit. Rename the top-level frames after their theme sections (Header, Hero, Featured collection, Footer), delete tracking and widget noise, and flatten only what you will never edit again.

From there, a redesign is a normal Figma job. You are marking up a real layout instead of redrawing it from screenshots, and every spacing value you measure came from the live theme. If you want to try it on one page, UnHTML starts free.

Questions

Can I import a Shopify store that is still password protected?
Only if the file you capture shows the real storefront. Private mode shows a password page to visitors, so saving the store URL gives you that page. Enter the password in your browser first, or use a draft theme preview link, then save the page.
Do I need theme code access to import a Shopify storefront?
No. The import works from the rendered page, saved as a self-contained HTML file, a Safari web archive or a scene.json from the capture CLI. Theme files help you read the section structure but they are not required.
How many layers will a Shopify home page use?
It depends on the theme and the number of sections, blocks and product cards. The free plugin stops at 500 layers per import. If a long home page passes that, import it in parts or use Pro, which has no cap.
Is the imported storefront a pixel-exact copy?
No. Missing fonts are substituted and listed in the import report, and layouts that cannot be reproduced fall back to absolute positioning. The result is faithful, editable layers, which is what a redesign needs.