Export a Figma selection to HTML
Take one selected design subtree into a portable HTML-and-assets package. Use the export as a visual starting point, with a report explaining what was simplified or rasterized.
A visual handoff, not a production code generator
The exporter reads one selected Figma subtree and produces a ZIP containing index.html, assets, export-report.json and a README. It supports a useful subset of text, geometry, Auto Layout, fills, images and vectors.
It does not recreate application logic, prototype interactions, component properties, a responsive design system or design-token relationships. Unsupported nodes can become static fallbacks, with warnings in the report.
This is not a guarantee of pixel-identical HTML → Figma → HTML round-tripping. Review the package as a reference or starting point before adapting it for a real application.
Select, export and inspect the package
Select exactly one frame, group or other supported design root in Figma. Open the plugin, choose More, then Tools, and find Export selection to HTML. Start with a small frame containing text and an image.
Start export and wait for scanning, asset collection and packaging to complete. The manual export reads the selected tree without changing its nodes, styles or variables. Do not change the selection while the export is being prepared.
Extract the ZIP without moving index.html away from its assets directory. Open the HTML locally and compare the result with the selected frame. Read export-report.json to see the reported degradations, not only the visible preview.
What stays structured and what may become an image
Supported text becomes escaped text with available style properties. Compatible Auto Layout patterns become a bounded Flexbox representation. Image fills are packaged as assets, while vector shapes can become sanitized SVG images.
Complex transforms, mixed text styles, gradients and effects can be approximate. Unsupported surfaces may use PNG fallback or a visible placeholder if the fallback also fails. The export does not silently label those results as fully structured HTML.
Fonts are not downloaded or bundled. A browser without the original font may produce different wrapping. Resolve font licensing and availability separately before using the result outside your design environment.
Keep the selected subtree manageable
The current safe subset allows up to 2,000 nodes, a depth of 32 and 128 assets. The final ZIP must stay below 24 MiB. Individual assets, text and total payloads also have limits.
If a large page exceeds the boundary, export a smaller section instead of repeatedly retrying the entire canvas. A clear section-level package is often more useful for implementation than a large flattened page.
The manual download path differs from MCP/REST export. A remote export intentionally uploads the result to the configured automation service, so review content permissions and the destination before requesting it.
FAQ
Questions before you import
Practical answers for export selection to html.
Does export modify my design?
The manual exporter reads the selected subtree and does not edit its nodes, styles or variables. Keep selection and content stable during the operation.
Is the output production-ready application code?
No. It is a bounded visual HTML subset with assets and a degradation report. Application behavior, accessibility review and production engineering remain separate work.
Are my fonts included?
No. Fonts are not downloaded or packaged. Browser font availability can change text metrics.
Can I export all selected frames in one operation?
The manual workflow requires exactly one selected root. Export a containing frame or handle separate roots individually within the supported limits.