Update imported Figma designs

Start with a result the plugin manages

Select a root created by HTMLtoFigma, then open the plugin's update action. Imported roots carry source and revision information used to identify the result safely. An arbitrary Figma frame is not automatically eligible for this workflow.

For a website capture, use Update from original source or the available Re-import URL relaunch action. For a Code import, edit the HTML/CSS and update the selected managed result. A source URL used to resolve editor assets does not turn that editor draft into a live website import.

Review, update, inspect

Confirm the selected root and source before starting. Review the capture settings, including widths, themes, Auto Layout and styles. Website re-import can reuse saved settings; an explicit editor update uses the chosen current settings.

Run the update and wait for Figma layer creation to finish. The importer prepares replacement content before committing it to the managed root. Inspect the result at the same width as the source and complete any font review.

The managed root's identity, name and position are preserved through a successful update. This does not promise that every descendant layer keeps its identity or that every hand-authored edit is merged into the new capture.

• Select the intended imported root.
• Confirm the source and requested settings.
• Resolve any manual-edit warning before replacing content.
• Inspect the updated result and its revision.

Manual changes are a decision, not an invisible merge

If the managed content has changed since import, the plugin can require explicit confirmation before replacing it. This protects against silently overwriting design work that no longer matches the saved baseline.

Keep a separate design copy when you want to explore freely while maintaining a source-synced reference. Re-import refreshes that reference; it is not a three-way merge engine for arbitrary Figma edits.

Do not switch selection or modify the target while an update is committing. The importer checks the expected target and revision to reduce accidental overwrites.

When an update cannot complete

An inaccessible source, a changed target, or an import failure can stop the update. The old managed content is retained when the replacement cannot be committed safely. Read the error before retrying.

For a browser-session capture, return to the extension and capture the current page again if necessary. A local file cannot become a fresh authenticated browser view by itself.

Use the original import workflow to isolate the issue: verify the URL or code, reduce the selected sizes, and check assets. For support, include the version and sanitized error details rather than private page contents.