Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchIf html.to.design imports only the visible portion of a long webpage, use Chrome DevTools Device Mode to increase the viewport height, then capture the page with the extension’s Capture full page option. Import the resulting .h2d file into the html.to.design Figma plugin. This is the vendor’s workaround for pages whose unusual height or scrolling behavior prevents a normal full-page capture; it is not guaranteed to work on every site. See html.to.design’s “Not capturing full page” guidance.
Choose the right import route
Use the route that matches the page you need to bring into Figma. Direct URL import is convenient for publicly accessible pages. Browser-extension capture is the better fit when you need a private or local page, an authenticated session, or the specific state currently open in your browser.
As an Amazon Associate I earn from qualifying purchases.
| Situation | Route | Handoff |
|---|---|---|
| Public page with an open URL | In the plugin, open the Web tab, paste the URL, and select Import. | The page imports directly into the plugin. Web import instructions |
| Private, local, or logged-in page; or a particular browser session | Capture the page open in your browser using the html.to.design extension. | Send it to the plugin, or save a .h2d file and drop that file into the plugin. Browser extension instructions |
| A long page is cut off by capture | Use the extension with Chrome DevTools Device Mode and a very large viewport height. | Import the generated .h2d file into the plugin. Troubleshooting guidance |
Capture a long page with a taller viewport
The steps below use Chrome because the documented workaround relies on Chrome DevTools Device Mode. The documentation does not prescribe a universal viewport height, so adjust it for the page rather than treating any one number as a standard.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems- Install the html.to.design browser extension if you have not already, then open the target page in Chrome. The extension captures the page as it appears in that browser session. Extension setup and capture details
- Open Developer Tools. In Chrome, open DevTools from the browser’s menu or use the keyboard shortcut for your operating system.
- Enable Device Mode by selecting the device toolbar icon in DevTools. This displays the device viewport controls.
- Increase the viewport height substantially. Enter a very large height in the viewport dimensions. No single height is documented as suitable for every page; choose one large enough for the content you want to capture.
- Run the html.to.design extension and select Capture full page.
- Import the capture into Figma. Drop the generated
.h2dfile into the html.to.design plugin. The imported page is represented as editable design layers.
Why the capture may stop at the visible area
html.to.design says it normally captures a webpage’s full length, but some sites handle body height, scrolling, or item display unusually. In those cases, capture may return only what is visible. The tall Device Mode viewport is the vendor’s workaround for that behavior, not a guarantee for every page.
#1 Best Overall
The html.to.design feature page also describes editable imports and support for overflow scrolling and fixed or sticky elements in prototypes. Those product capabilities do not establish that every site will capture correctly. html.to.design feature overview
Or skip the browser setup
If you need a screenshot or PDF rather than editable Figma layers, ScreenshotNeo can return one with a single API request. It does not replace html.to.design’s editable-layer import workflow.
cURL example (see the ScreenshotNeo API documentation):
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed. Its MCP server lets AI agents use screenshot tools, and the free plan includes 1,000 screenshots per month with no card required; paid plans start at $5 for 3,000.
Sign up for ScreenshotNeo’s free plan.
Common problems and what to try
- The imported result still shows only part of the page: confirm that Device Mode was enabled and that you increased the viewport height before selecting Capture full page. Some sites’ height or scrolling behavior may still defeat the workaround.
- You are importing a page behind a login: use the browser extension on the page open in your authenticated session rather than relying on a public-URL import.
- The URL import cannot access the page: for a private, local, or session-specific page, capture it in the browser with the extension and send the capture to the plugin or save the
.h2dfile locally. - You have a capture file but are not sure how to hand it off: drag and drop the generated
.h2dfile into the html.to.design Figma plugin.
Cost and allowance
html.to.design’s official overview states that the product offers 12 free imports per month; the page does not state the year for that allowance. Check the current product page for availability and terms before relying on it. html.to.design documentation
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
