Every Figma-to-web tool, ours included, is only as good as the file you feed it. These are the checks worth making before you publish anything, roughly in order of how much rework they save. None of them take long.

1. Every page is a top-level frame, named properly

Most publishing plugins enumerate the top-level frames on each Figma page, meaning direct children of the page. A frame nested inside another frame is a component of a layout, not a page, and won't show up in the list. Sections are worth watching too, because a Section is a different node type and frames tucked inside one may not be visible to the plugin.

So: drag your page frames out to the canvas top level, and name them like pages. Home, About, Pricing, not Frame 247. You'll be picking these from a dropdown and future-you will not remember which Frame is which.

2. Every page has a mobile frame

More than half your visitors are on a phone. A 1440px desktop design scaled to a 390px screen gives you unreadable body text, and there's no automatic fix because the mobile layout involves decisions only you can make about what stacks, what hides and what gets cut.

Duplicate the desktop frame, resize to 390px, rearrange. This is the single item on this list that saves the most work, and the one people skip most often. Details in Figma responsive web design.

3. Fonts are either on Google Fonts or licensed for the web

A font renders in a browser only if the browser can download it or the visitor already has it installed. Figma will not give you the font file, and a desktop font licence almost never covers web embedding, so converting a desktop .otf to WOFF2 doesn't make it legal to serve.

Check each typeface in your file against Google Fonts. If it's there, you're fine. If it isn't, either swap to the closest Google Fonts equivalent or buy a webfont licence and self-host the WOFF2. Doing this before you publish is a ten-minute job. Doing it after means re-picking type across every frame.

While you're in there, note which weights you actually use. Loading only 400 and then setting text in 600 makes browsers fake the bold, which looks noticeably worse than real weight. More on all of this in Figma fonts not working on your website.

4. Text layers are still text layers

If you flattened a headline to vector, or pasted it in as an image, it stops being text. It can't be selected or copied, screen readers skip it, search engines can't read it, and it goes blurry when it scales.

Flattening is destructive in Figma and you can't undo it later from the layer itself, only from version history. Check your headlines and logos specifically, because those are the ones people outline. Converters generally never rasterize a real text node, so as long as the layer is still a TEXT layer you'll get real HTML text out the other end.

5. Images are compressed before they go in

Image layers get exported as raster PNGs at publish time. Nothing downstream can recover detail you already threw away, and nothing can shrink a source file you never optimised. A design carrying ten 4MB photographs becomes a page carrying ten large PNGs, and mobile visitors on a weak connection will leave before it paints.

Run your photos through something like Squoosh or ImageOptim first, and size them roughly to the box they'll occupy rather than dropping in a 6000px camera original that renders at 400px.

Also check your icons and logos are vectors in Figma rather than screenshots someone pasted in.

6. Links are set on the things that look clickable

Buttons, nav items, logo, footer links, social icons. Every element that a visitor will click needs a link set, either through your plugin's link options or as a prototype connection, depending on the tool.

The one people miss is the logo in the header, which everyone expects to go home. Walk your own site as a visitor and click everything that looks clickable.

7. Coordinates rounded, hidden layers deleted

Figma will let a layer be 247.3333px wide. Browsers round fractional pixels when they paint, and the drift shows up as one-pixel seams between elements that were meant to align. Select all and use Round to pixel.

Then delete the hidden layers, the old versions parked off to the side, and the scratch work. Anything still in the frame is something the converter has to reason about, and off-canvas junk has a habit of turning into a mysterious horizontal scrollbar.

8. Read the copy one more time

Publishing makes typos public. Also check your longest strings rather than your prettiest ones, because text reflows differently in a browser than in Figma and a headline that fits on one line in the design can wrap to two on the site.

Once that list is clean, most of what goes wrong between Figma and the web has already been ruled out. If you want to run it through our Figma plugin, it publishes from the frames directly.