Missing HTML attributes, styles or frontend frameworks

Weblify supports common HTML attributes, layout styles, and frontend output formats. Some advanced Figma properties, browser CSS, embedded content, and interactive behavior may still need manual adjustment after generation or import.

The Chrome extension does not open on a page

Browser-internal pages and the Chrome Web Store do not allow extensions to inject page controls. Open a regular website tab, refresh it after installing the extension, then select the Weblify extension icon again.

An imported website looks different from the live website

Wait for lazy-loaded content, fonts, and images to finish appearing before copying the page. Interactive applications, embedded content, unsupported CSS, and assets blocked by the source website may still produce differences after pasting into Figma.

Copied content does not paste into Figma

Wait for the extension to show Copied to clipboard, return to the Figma canvas, and paste with Command + V on macOS or Ctrl + V on Windows. If another clipboard item appears, copy the page or element again immediately before pasting.

VPN may be required in China

Note, if you're in China, the accounts server may be blocked by "The Great Firewall of China". If you're seeing an activation error, despite using a valid key, you will likely need to use a VPN to resolve the issue.

'An error occurred while loading the plugin environment'

This may happen in the Figma desktop app if the Use Developer VM debug setting in Figma is enabled by mistake; you can make sure it's turned off by right-clicking anywhere on your Figma canvas, hovering over Plugins, then hovering over Development, and making sure that the Use Developer VM is unchecked; after it is unchecked (and does not have a tick icon next to it), re-running the Figma plugin should work as expected.