Pro Feature

Landing Page Importer. One URL in, one file out.

Import a webpage from its URL into a self-contained HTML file, with CSS, JS, images and fonts brought in and self-hosted. Migrate it, inspect how it's built, or prototype offline, then rework it with AI.

Import from URL Open the editor

CSS · JS · images · fontsSingle portable HTML fileEdit with AI after importing

How it works

From URL to editable HTML in seconds.

Paste a URL

Click 'Import from URL' and paste the address of a page you own or have permission to use.

We bring in everything

Our server fetches the page with a real browser User-Agent, then follows the full asset graph — stylesheets, scripts, images, web fonts, lazy-loaded media, OG images — and downloads them all.

Assets are rehosted on our CDN

Every asset is uploaded to htmlhost's R2 CDN and all URLs in the HTML and CSS are rewritten to point to our servers. No broken paths, no hotlink dependency on the original domain.

Edit with AI and publish

The imported page opens in the editor as a single portable HTML file. Use the AI editor to rework any element, then publish it to your own htmlhost.co URL.

Asset coverage

Every asset. Not just the HTML.

Most tools fetch the HTML and stop. We follow the full asset graph — recursively.

Stylesheets & @imports

CSS files are downloaded and scanned recursively for @import rules and url() references — fonts and background images nested inside external CSS are captured too.

link[rel=stylesheet] · @import · url()

JavaScript bundles

Script tags are fetched. Self-contained single-bundle SPAs are inlined. Code-split chunks that require a build system are identified and skipped safely.

Images & srcsets

Every img src, srcset, picture source, poster, data-src, and data-lazy-src is discovered and downloaded — including lazy-loaded and responsive images.

img · srcset · data-src · picture

Web fonts

Font files referenced via @font-face, link[rel=preload as=font], and CSS url() are downloaded and rehosted. No more Google Fonts fallback dependency.

woff2 · woff · ttf · otf

Next.js & framework images

Next.js /_next/image optimised URLs are decoded to extract the original image and download it directly — not the CDN-resized variant.

/_next/image · CDN-aware · Vercel

OG & meta images

Open Graph and Twitter card images referenced in meta tags are included so your imported page has a complete head section, not broken social previews.

og:image · twitter:image · meta

Use cases

Why people import pages from a URL.

Migrate a site off another host

Import an old site hosted elsewhere, clean it up in the editor, and publish it on htmlhost.co — without touching a config file.

Back up your own pages

Keep a portable, editable snapshot of a page you run before a redesign or a platform change. Unlike an archive screenshot, it stays fully editable.

Inspect how a page is built

Open a page's HTML, CSS and scripts side by side in the editor to see how its layout, type and responsive rules fit together.

Redesign with AI

Import a page you own, then click any section and describe the change. Faster than rebuilding it from scratch.

Prototype offline

The single HTML file is self-contained. Open it in any browser without an internet connection — fonts, images, and styles all work.

Hand a page to a developer

Give a teammate or client one editable project with every asset in place, instead of a folder of broken Save As files.

Why htmlhost

Better than Save As. Better than HTTrack.

Capability	htmlhost Importer	Browser Save As	HTTrack
Single portable HTML file	✓	✗	✗
Web fonts downloaded	✓	✗	Partial
Lazy-loaded images captured	✓	✗	✗
CSS @import chains followed	✓	✗	✓
Next.js / SPA support	✓	Partial	✗
Assets rehosted on CDN	✓	✗	✗
Edit result with AI	✓	✗	✗
No software to install	✓	✓	✗

FAQ

Frequently asked questions.

What gets imported?

Everything the page needs to render: stylesheets, JavaScript bundles, images, fonts, background images from CSS url(), srcsets, lazy-loaded images, OG images, and more. Assets are brought in and served from htmlhost's CDN, so the imported page doesn't depend on the original server.

Will the imported page look the same as the original?

In most cases, yes. The importer fetches with a real browser User-Agent and follows the full asset graph. Some pages rely on server-side rendering, sign-in sessions, or live API calls that can't be captured, but the static design and layout come through.

Which pages can I import?

Pages you own or have permission to use. It's built for legitimate work: moving your own site off another host, backing up your pages, inspecting how a page is built, or prototyping a redesign offline. Republishing someone else's content, branding or copy as your own is prohibited by htmlhost's Terms of Service.

Why is this better than browser Save As?

Browser Save As produces a folder of disconnected files and breaks on CSS @imports, web fonts, lazy-loaded images, and JS modules. The Landing Page Importer produces a single portable HTML file with everything inlined or self-hosted: no broken paths, no missing fonts.

Is this a Pro feature?

Yes. Import from URL is available on the htmlhost.co Pro plan: the import runs server-side, downloads every asset and rewrites it to our CDN, which takes compute and bandwidth the free plan doesn't cover. Moving your own WordPress site is free once you verify you own it.

Can I edit the imported page with AI?

Yes, that's the intended workflow. Once imported, the page opens in the htmlhost editor. Click any element, describe the change in plain English, then publish it to your own URL.

Pro feature

Import a page from its URL. Edit it with AI.

One URL in, one portable HTML file out. Rework it with the AI editor and publish to your own URL in seconds.

Import from URL