1. LandOffer
  2. Blog
  3. All articles
  4. Need a Self-Hosted Portfolio After Framer? Compare Exportable Replacement Workflows

Job search

Need a Self-Hosted Portfolio After Framer? Compare Exportable Replacement Workflows

Compare visual code-export and source-based rebuilds, identify features that need replacement, and plan the next update before changing hosts.

9 min readLandOffer team

If your portfolio must run independently of Framer, plan a replacement rather than budgeting for a built-in HTML download. Framer’s current help says it does not offer that export. A custom domain, exported images and a reverse proxy each solve a different problem; none supplies a complete independent website bundle from the Framer editor.

This LandOffer.ai guide uses official public documentation inspected October 22, 2026. We did not export a site, run a migration, buy a plan, configure hosting or publish anything. Both completed planning examples are original fiction. Start with the work samples relevant to recent roles on LandOffer.ai, then decide how much publishing infrastructure those samples need.

An architectural model workshop separates an existing visual design from a newly constructed independent gallery

Define what independent hosting must mean

Define independent hosting by the files and services the receiving host must be able to run. For a small public portfolio, that might be HTML pages, CSS, JavaScript and images that work without a Framer content origin. For an editable portfolio, you also need maintainable source material and a repeatable way to produce the next version. A downloadable folder and an understandable editing workflow are related deliverables, not interchangeable ones.

The Framer HTML export explanation says its publishing and optimization services depend on Framer infrastructure. Its position is explicit: it does not provide published sites as standalone HTML or static website bundles. That is the relevant product limitation for this decision, rather than whether a browser can save something that resembles a page.

Decide why the requirement exists. You might need a host your organization already approves, an independently preserved public work sample or the ability to change providers later. If you only want your own domain name, the same help page says Framer supports connecting one while continuing to host the site. That narrower requirement may not justify rebuilding during an active job search.

Separate images, a proxy and a transferable website

Framer’s asset export help describes PNG and JPG output from its desktop app. A page image can be useful visual reference. It does not preserve selectable narrative, semantic headings, navigation or an editable website as a working HTML project. Keep original diagrams and permitted project media separately instead of treating screenshots as the entire portfolio source.

The reverse-proxy guide describes serving requests through another infrastructure layer while retaining Framer as the content origin. This may meet a delivery requirement, but it does not meet a requirement to remove the underlying Framer dependency. Its Advanced Hosting plan conditions and proxy compatibility rules also deserve separate review if delivery control is the real goal.

Third-party tools may advertise downloading a published site. This guide does not verify those products or claim their output is complete, licensed for every asset or maintainable. Before relying on any such route, require evidence for your own necessary pages and behaviors, dependency removal, permitted asset use and the next editing cycle. Checking the next editing cycle helps you avoid paying for a copy you cannot maintain; a homepage screenshot cannot establish that capability.

Choose between a visual rebuild and a source-first rebuild

Two documented replacement workflows address different constraints. Webflow can support visually rebuilding a modest static portfolio and then exporting eligible site code. Astro can support rebuilding a portfolio as a source project that generates static pages. Neither is documented here as a direct Framer project importer.

Requirement Webflow rebuild with code export Astro static rebuild
Main editing approach Recreate the site in a visual builder Maintain content, layouts and assets in a source project
Independent deliverable Exported HTML, CSS, JavaScript and assets within documented limits Static build output, normally in dist/, plus the source you retain
Main dependency to examine Workspace export access and hosted features excluded from export Build environment, dependencies and any server-rendered routes
Work you still own Rebuilding content/layout and replacing excluded services Implementing layout, content structure and the update process
Poor assumption A paid Site plan alone includes code export Every Astro project can run on a static-only host

Choose an editing workflow you can keep using after the first release. Someone who updates case studies through a visual canvas may accept periodic export work. Someone comfortable maintaining a repository may prefer source files and a reproducible build. The generator changes your publishing workflow; the case study still needs a clear account of your own contribution.

Read Webflow’s export exclusions before rebuilding there

The official Webflow code export guide places code export on paid Workspace plans and explicitly excludes Site plans as the source of that entitlement. Check the applicable Workspace before buying anything; this comparison does not provide a checkout quote or assume every paid product includes export.

Its static output also has material limits. CMS-bound content and functionality, ecommerce, User Accounts, localized content and code components are excluded. Collection lists and template pages will not carry their bound content as a functioning CMS site. A separate CSV backup of Collection data does not reconstruct the display or editing system on another host.

Forms, site search and password protection do not continue as equivalent exported services. A formerly protected page must not become a public copy merely because its visual layout exports. For a public portfolio, an intentional contact link may be enough; confidential case studies need a separately justified access arrangement rather than a cosmetic password field.

Include the exported JavaScript, Webflow component CSS and site-specific styles in the handoff: the guide notes that interactions and components depend on them. It also warns that manual edits can break components. Decide which copy becomes authoritative after export, so later visual edits and hand-edited files do not silently diverge.

Understand Astro’s source and runtime responsibilities

Astro’s deployment overview documents a build process and a default dist/ output directory. Its rendering guide says pages are prerendered by default. That makes a static portfolio a documented workflow, but the existing Framer layout still needs to be recreated and the content organized.

On-demand rendering changes the requirement. It needs an adapter for a particular server runtime; a personalized page or endpoint cannot be assumed to work by placing static files on any host. Identify these dependencies before choosing a host, rather than discovering them after a design is complete.

For a small portfolio, start the planning conversation with public case-study pages, ordinary navigation and optimized project media. Add a server or external service only for an actual requirement. Keep source, dependency information and build instructions alongside the generated output. A copy of dist/ may preserve one release, while the source and build process determine whether you can revise it later.

An archivist distinguishes transportable artwork and source materials from a cabinet of remaining dependencies

Worked asset: a three-page replacement decision

Maya’s fictional portfolio contains a home page and two original public project write-ups. She wants independent hosting and can maintain a small source repository. Her completed replacement record is below. These are planning estimates and intended outputs, not results of an actual migration.

Existing item Replacement specification Completed decision
Home page Short introduction, two project links and contact link Rebuild as one static page
Scheduling demo Narrative and two original diagrams Rebuild as a static case study; retain diagram originals
Search prototype Narrative and one original screenshot Rebuild as a static case study; describe demo limits
Animated page entrance Decorative motion only Omit from the first replacement
Contact form No requirement to collect structured submissions Replace with a contact link
Old draft case study Unfinished, outside the public scope Exclude from the replacement

Her complete handoff brief reads: “Three public pages: /, /projects/scheduling/ and /projects/search/. Preserve original narrative and three permitted media files. Supply source, build instructions and generated static output. No forms, login, CMS or runtime personalization. Navigation must link all three pages; the two case studies must explain my contribution and limitations.”

Maya budgets two hours for content preparation, six for rebuilding layout, three for link and layout review and two for handoff notes: thirteen hours total. With two three-hour evenings each week, twelve hours fit into two weeks and one hour remains for the following week. She does not describe it as a two-evening task.

Her finished decision is to shortlist an Astro static rebuild because her scope and editing ability fit that workflow. She keeps the existing portfolio available while preparing the replacement and makes no domain change in this plan. If rebuilding consumes time needed to improve the weak search write-up, she will simplify presentation further before expanding the website.

Worked asset: reject a visually complete but incomplete handoff

Jon’s separate fictional portfolio has four case-study records in a CMS, a contact form and a password-protected draft. He prefers visual editing and is considering a Webflow rebuild. His first proposed handoff is “export the ZIP when the design looks right.” His completed dependency review changes that brief.

Dependency What the receiving host needs Decision recorded
Four CMS case studies Readable public pages with the intended content Rebuild as ordinary static pages for this release
Case-study editing One authoritative source and a repeatable update method Keep builder editing authoritative; document each later export
Contact form A supported submission destination and handling rules Remove for now; use a contact link
Protected draft Access control beyond appearance Keep out of the exported public site entirely
Existing project paths Explicit mapping from old links to new destinations Preserve four project paths where feasible; record exceptions
Theme assets Permitted local files and required scripts/styles Inventory them; unresolved permission blocks inclusion

His full revised brief is: “Recreate four approved public case studies as static pages. Exclude the protected draft and form. Deliver all exportable styles, scripts and permitted images, a four-path map and instructions for the next builder edit/export. Identify the paid Workspace that permits export. A CMS CSV alone does not satisfy the page-content requirement.”

Jon’s illustrative effort is four hours of content reconstruction, five of layout work, two of dependency review and three of handoff and page review: fourteen hours. At a personal planning value of $30 per hour, that is $420 of time, before any builder, host or domain charges. The $420 covers only Jon’s assumed fourteen hours at $30; it excludes vendor fees and does not estimate another person’s migration.

His decision remains conditional: use the visual-export route only if the reduced static scope and repeat-export workflow are acceptable. Otherwise request a source-based rebuild estimate. A polished preview does not override the unresolved asset permissions, and he does not release the excluded draft to make the package appear complete.

Keep the next revision in the purchase decision

Before committing, ask what happens when you add a fifth case study, correct a broken image or change an old project path. Name the source of truth, the files needed to rebuild and the person responsible for the next release. Budget that recurring work alongside any subscription, hosting and domain costs; this guide does not assume a free host or a fixed replacement price.

The practical choice is a replacement whose exported deliverables and maintenance responsibilities match your actual portfolio. Keep a hosted Framer workflow if its dependency is acceptable. Choose an independent static workflow when that requirement justifies rebuilding, and reduce the first version to the evidence a reader needs. To choose those samples, browse recent roles on LandOffer.ai and choose one relevant contribution, explain its scope and limitations, and build only the pages needed to present it.

Sources and Further Reading

Official public pages inspected October 22, 2026; descriptions are not completed export or deployment tests. Webflow’s page was readable in the browser while its direct GET returned HTTP 403.