HTML.to.design Cannot Capture a Website: Common Causes and Fixes

If html.to.design cannot capture a website, first check how you can access that page. Use the plugin’s Web tab for a public URL that loads without signing in. If the page needs a login, VPN, browser session, or a CAPTCHA you have already solved, capture the page with the html.to.design browser extension while it is open in your browser. For a page that is cut off or looks unlike a phone, use the specific viewport or user-agent workarounds below.

html.to.design combines a Figma plugin and browser extension to turn captured websites into editable Figma designs. The URL importer works with publicly accessible pages; the extension can capture a page currently visible in your browser. html.to.design overview

1. Identify which kind of capture is failing

What you see	Likely cause	First step
The URL import cannot load the page	The page is private, login-protected, VPN-only, or stopped by a CAPTCHA	Open it in your browser and use the extension after gaining access
Only the first screen appears	The site handles scrolling, body height, or content display in a way the importer does not capture as a full page	Try the documented large-viewport workaround
The result does not resemble a phone	The site may select its layout using the browser user-agent	Capture through the extension with a mobile user-agent configured in DevTools
The result is in the wrong language	The site’s language-selection system may not respond as expected to URL import	Load the desired language visibly in the browser, then capture that page

Start by opening the exact page in a normal browser tab. If it does not render there, the importer cannot capture the intended page either. Resolve the access or rendering issue in the browser first, then select the capture route that matches the page’s access state.

2. Choose the right capture route

Use the Web tab for a public page

Choose the Web tab when the page is public and its URL opens without a login or a browser-only session. Enter the URL and import it. This is the direct route for public pages, but it is not a way to import private pages or bypass CAPTCHA challenges. Import a page from the Web tab

Use the browser extension for a page you can see

Use the extension when the page is behind a login, available only on a VPN, depends on an existing browser session, or is already rendered after you solved a CAPTCHA. Sign in or connect to the VPN in the browser, navigate to the target page, and capture the visible page with the extension. You can send the capture to the plugin or save it as a local .h2d file and import that file. About the browser extension · Import a private webpage

Open the page in the browser where you are authenticated or connected to the required network.
Confirm the page is showing the correct content, language, and state.
Capture it with the html.to.design extension.
Transfer the capture to the plugin, or save the .h2d file and drop it into the plugin.

The vendor says that when you export a local .h2d file, the file is stored locally and the captured page data does not reach its servers. That statement applies to the local-file workflow; it should not be assumed to describe sending a capture directly to the plugin. Private page capture and local files

3. Fix common capture problems

The Web tab expects a publicly accessible page. Sign in, connect to the VPN, and open the target page in your browser, then capture it with the extension. If you need to move the result separately, save a local .h2d file and import it.

A CAPTCHA blocks the URL import

The URL importer does not solve CAPTCHA challenges automatically. Complete the challenge in the browser, make sure the page you want is visible, and capture that browser page with the extension. Do not keep retrying the public URL importer as a CAPTCHA bypass.

The full page is cut off

Some sites manage body height, scrolling, or the display of page items in ways that interfere with full-page capture. The vendor documents a workaround using Chrome DevTools Device Mode with a very large viewport height, followed by a full-page capture with the extension and import of the resulting .h2d file. This is a remedy for some site behaviors, not a guarantee for every page. html.to.design full-page capture guidance

Open the page in Chrome and open DevTools.
Enable Device Mode and set a very large viewport height.
Use the html.to.design extension to make a full-page capture.
Save the capture as a .h2d file and import it into the plugin.

The mobile capture looks different from a real phone

Some sites choose their layout based on the user-agent, so changing only the viewport dimensions may not reproduce a phone-specific page. The vendor recommends capturing with the browser extension and changing the user-agent in Chrome DevTools Network conditions, then recapturing. Results depend on how the site detects devices; the workaround is not a promise of an exact match on every site. Capture with a custom user-agent

The capture uses the wrong language

First load the desired language visibly in the browser and capture that state with the extension. The vendor notes that URL import may fail to select a language because some sites implement language selection in technically different ways. There is no universal language fix established for every site.

4. Troubleshooting checklist

Symptom	Cause to check	Action
Import cannot reach the page	It requires authentication, VPN access, or a browser session	Open it with the required access and use the extension
CAPTCHA appears	The importer has been challenged	Solve it in the browser, then capture the accessible page with the extension
Capture ends at the first screen	The site’s scrolling or content-height behavior interferes with full-page capture	Try Device Mode with a very large viewport height, extension full-page capture, and `.h2d` import
Mobile layout is unexpected	The site may use user-agent detection	Set a suitable user-agent in DevTools Network conditions and recapture with the extension
Wrong locale appears	The site may not respond to URL-based language selection	Load the desired language in the browser and capture the visible state
Extension capture is not the desired page	The browser may show a redirect, access error, or incomplete state	Verify the page contents in the browser before capturing
Neither documented route works	The site may have a behavior not covered by these workarounds	Check current html.to.design support guidance; the documented methods do not establish a universal fix

5. Practical limits, reliability, and time

Choose the route based on what the browser can access: public, unauthenticated pages fit the Web tab; authenticated or browser-session pages fit extension capture. A CAPTCHA must be handled in the browser before extension capture. For long pages and mobile mismatches, the large viewport and custom user-agent are targeted workarounds. They may require another capture attempt and are not guaranteed to work for every website.

If the page is large, capturing the full page can take more effort than capturing the visible viewport. Use the full-page route only when the design needs below-the-fold content. For private pages, the local .h2d transfer option also lets you keep the capture in a local file according to the vendor’s description; review its current documentation for workflow details.

Or skip the browser setup

If your goal is a clean image of a public webpage rather than editable Figma layers, ScreenshotNeo can return a PNG, JPEG, WebP, or PDF from one API request. It is a screenshot API and MCP server from Yorker Media. It does not convert a capture into editable Figma layers, so use html.to.design when that is the goal.

For a screenshot, use this cURL request. See the ScreenshotNeo API documentation for its options.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Equivalent Python request:

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

Equivalent Node.js request:

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer())));

ScreenshotNeo accepts cookie and consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing. Responses include X-Page-Verdict and X-Billed headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. The free plan includes 1,000 screenshots per month with no card, and paid plans start at $5 for 3,000 screenshots. These are screenshots for inspection or image output, not editable Figma layers.

FAQ

Can the html.to.design URL importer capture a page after I log in?

The URL importer expects a public page. Use the browser extension on the page already open in your authenticated browser.

Does the extension bypass a CAPTCHA?

No such capability is established. Solve the challenge in the browser, then capture the page you can access.

Will the full-page workaround always capture everything?

No. The vendor documents the large-viewport procedure for some pages, but does not promise it will work on every site.

Does ScreenshotNeo make an editable Figma design?

No. It returns screenshots or PDFs. Use html.to.design when you need editable Figma layers.