LayerPort

Example

A Framer portfolio, captured and self-hosted.

From a live Framer portfolio to a localized, editable project -- captured, optimized, and handed off as portable files.

Captured

Seven pages and their routes, with images, web fonts, and scripts localized to relative paths. Desktop, tablet, and mobile layouts captured so the responsive behavior matched the live site.

Optimized

Images converted to WebP and AVIF where it saved bytes, dropping page weight without visible quality loss. References rewritten across HTML, CSS, and JS.

Handed off

Exported as a sanitized ZIP with a deploy guide, then imported into Vercel with the vercel.json already in the ZIP. Version history kept every step reversible.

Weight, before and after

ItemValue
As captured3174 KB
After optimization640 KB
Measured on this capture, in kilobytes. The drop is image format conversion and nothing else — no markup was removed, and the pages render the same.

What shipped

Routes captured
7, including the two the navigation does not link to
Layouts reviewed
Desktop, tablet, phone — Framer publishes three; a capture that keeps one is a screenshot
Assets localized
84 files across images, fonts, CSS and JS
Handoff
Sanitized ZIP + vercel.json, imported into Vercel

Honest limits

  • Third-party embeds still load from their own origins
  • Form endpoints were re-pointed to the first-party inbox
  • Analytics and consent scripts were left pointing at their own origins, on purpose — rewriting them would have broken consent

Features · Workflow · Pricing · FAQ