Appearance

Troubleshooting & support ​

"Server not running" / "Cannot connect to server" ​

The plugin needs the local render server. In order:

  1. Run start-server.bat in the plugin folder and wait for the console to report the server is up, then click Check in the plugin.
  2. Already running? Something may be blocking localhost:3847 — a firewall rule, or another process on the port. Re-running start-server.bat frees the port and restarts cleanly.
  3. Make sure you extracted the package first — running from inside the zip archive fails in non-obvious ways.

"No Chromium-based browser found" ​

The server renders with an installed Chrome or Edge. Install either, or point the server at a specific browser by setting the PUPPETEER_EXECUTABLE_PATH environment variable to its .exe.

The plugin doesn't appear in Figma ​

  • Development plugins only load in the Figma desktop app, not in the browser.
  • Re-import it: Plugins ▸ Development ▸ Import plugin from manifest… and pick manifest.json from the extracted folder.

Fonts look wrong ​

  • Fonts are matched against what your Figma has installed; anything missing falls back to Inter, and the log names each substituted font — install the real font and re-import.
  • For imported HTML files, make sure the web-font <link> is present in the file. The server waits for fonts but gives up after 10 seconds; a retry usually catches a slow font CDN.

Icons appear as text or boxes ​

Icon fonts (Material, Font Awesome) are detected by their CSS classes and fetched as SVGs. If they import as squares or ligature text, check that the HTML actually includes the icon font's stylesheet link, and check the server console for fetch errors.

The import is missing sections of the page ​

  • Lazy content below the fold needs the auto-scroll pass to trigger — slow sites may need a second attempt.
  • Pages behind logins or bot protection can't be reached headlessly — use the Chrome extension to capture from your own browser instead.

Windows SmartScreen blocks the server ​

The .bat launcher is unsigned, so the first run may warn. Click More info ▸ Run anyway — the script only starts a local Node process.

Getting help ​

Reach out on LinkedIn — questions, bug reports, and feature requests are all welcome. When reporting an import problem, include the log output (and the URL or HTML file if you can share it); a Parse Only run captures everything relevant.