Job search
Webflow Review for a Job-Search Portfolio: Site Plans, Workspace Costs, and Export Limits
Current official plan and export evidence plus completed fictional CMS-budget and migration-dependency decisions for a job-search portfolio.
Webflow can support a job-search portfolio with visually designed pages and repeatable project records, but its two plan layers need separate attention. A Site plan covers a particular hosted site and its capabilities. A Workspace plan covers the working environment, including some staging, collaboration and code-export features. Choose each paid layer only when its capabilities are required.
Start with the work you want a reader to inspect. Compare recent roles on LandOffer.ai, choose the relevant case studies, and decide whether you need Webflow-hosted content management or an externally hosted static site. That choice matters more than buying the largest allowance.

Establish the current plans before comparing old prices
We checked official Webflow pricing and help documentation on October 20, 2026. Native public browser reads included the annual pricing display with Workspace plans expanded, the 2026 pricing-change article, plan overview and export guidance. Several automated help-page requests returned 403; full rendered help bodies were accessible and saved instead.
We did not create an account, design or publish a site, purchase a plan, connect a domain, export code, import content or upload private material. The completed examples below use fictional requirements. The migration cases apply documented dependencies; no export or deployed replacement was tested.
Webflow's 2026 plan-change guidance explains that CMS and Business Site plans were combined into Premium, with staged transitions for existing accounts. It lists Basic at $15 per month billed yearly or $25 on monthly billing, and Premium at $25 billed yearly or $39 monthly. Premium includes 20,000 CMS items and forty Collections under the documented update.
Older CMS-plan prices can therefore be misleading for a new purchase. Existing account timing can also differ. Read the selected offer and renewal details rather than assuming an older review describes your actual bill.
Separate the hosted site from the workspace
The plan overview distinguishes individual Site plans from Workspace-level capabilities. A free Starter Workspace can contain paid hosted sites. A paid Workspace is relevant when you need its additional tools, such as code export; paying for the hosted site alone does not unlock that export.
Evaluate the two purchases against separate requirements. Where will the portfolio run? Does it need a custom domain on Webflow hosting? Will its case studies be managed as CMS records? Do you need to export static files to maintain elsewhere? Answering those questions avoids adding an unnecessary subscription merely because both appear in the same pricing interface.
For a solo job seeker, collaboration capacity and additional seats may have little immediate value. A reviewer opening your public portfolio is not necessarily a collaborator who needs a Workspace seat. Do not purchase editing access to solve a public-site navigation problem.
Domain registration is another separate decision. A plan that supports connecting a domain does not establish that you own the desired name, have configured it correctly or have paid its renewal. We performed no domain or DNS actions.
Understand the free and paid portfolio boundaries
The current pricing page lists a free Starter site on a Webflow.io domain with two static pages, limited CMS and other limits. Basic adds a custom domain and 300 static pages but is intended for sites without a CMS. Premium is the content-management option. A large static-page allowance does not mean Basic includes CMS records.
The same page shows the team-oriented Core Workspace at $19 per month billed yearly, with code export and enhanced staging. This is an example of a paid Workspace tier, not a claim that it is the only Workspace offering or the right purchase for every applicant.
Choose content structure before counting capacity. Three carefully maintained static case studies may need no CMS. A recurring project library with consistent fields can benefit from structured records, but it also adds content-model and migration decisions. Neither structure proves the applicant's technical contribution without the actual explanation and evidence.
Worked plan allocation: six case studies, one content model
Consider fictional applicant Niko, who wants a portfolio with six case studies plus an introduction and contact page. Assume Niko plans to add projects regularly and wants the same fields on each case study. These are planning inputs, not an account or portfolio we inspected.
Niko defines one Projects Collection with six records. Each record would contain a title, project purpose, personal contribution, evidence route and verification boundary. The collection is a content model; it does not create or verify the projects themselves.
| Fictional requirement | Completed allocation | Reason |
|---|---|---|
| Six regularly maintained project records with a shared structure | Premium Site plan for the intended Webflow-hosted CMS | Basic's static pages do not supply the requested content-management function |
| One person editing; no present export requirement | Starter Workspace retained | No stated need for paid Workspace tools |
| Custom domain | Track ownership and registration separately | Hosting capability does not supply ownership or a registrar renewal price |
| A future external-hosting experiment | Leave as a separate future decision | Do not buy an export tier solely because migration might someday be useful |
At the checked annual-billing rate, Niko budgets 12 × $25 = $300 for the Premium Site plan before tax and any add-ons. The free Workspace adds no paid Workspace charge in this scenario. Domain costs remain unspecified rather than being silently included in the $300 figure.
If Niko later adds the cited Core Workspace on annual billing, its separate 12 × $19 = $228 would make those two selected subscriptions $528 before other costs. That is a conditional combination, not the minimum price of having a portfolio. A static Basic site at the checked annual rate would instead be $180 for its Site plan, but it would not meet Niko's stated CMS requirement.
Niko selects the hosted CMS route and declines the paid Workspace for now. The decision follows the actual publishing model, not the fact that six projects exceed the Starter site's two static pages. CMS items and static pages are different counts.
Write case-study fields that preserve evidence boundaries
Niko's completed content model includes a required contribution paragraph rather than only a thumbnail and project title. Its prompt is: “What did I implement, what did others provide, and where can the reader inspect the relevant work?” Another field records what was actually tested and what remains unverified.
A sample entry might say that a project uses synthetic data and demonstrates a particular transformation, while its linked explanation identifies the input and expected output. It should not claim customer adoption or production ownership merely because the page looks finished. The field structure helps maintain consistent disclosure; it does not validate the claims automatically.
Treat source links, recordings and downloadable material as separate artifacts. A public Webflow page does not make a private repository accessible. Check the exact destination and sharing permission before a real application, and keep a readable explanation on the page for someone who chooses not to open the demo.
For a job-search portfolio, consistency is useful only when it makes the work easier to assess. Select each Collection record for its relevance and defensible contribution evidence. Keep the selected examples relevant to the role and accurate about your individual contribution.
Static code export has a specific scope
Webflow's code-export guide says paid Workspace plans can export HTML, CSS, JavaScript and assets. It explicitly excludes CMS content and functionality, code components and certain other dynamic content. Collection lists can be empty and field-bound template content absent after export.
The guide also says site search, native form processing and password protection do not carry over as functioning equivalents. A ZIP file is therefore not evidence that the hosted portfolio has been reproduced elsewhere. Do not publish exported material assuming a previous password gate remains in place.
An exported static site may still be a useful format for an appropriate project. The question is which dependencies you actually used and what must replace them. We performed no export, hosting or compatibility test, so this review makes no claim that a particular interaction or asset survived a migration.

Worked migration audit: a package is not a finished replacement
Suppose Niko later considers external hosting. The fictional site has two static pages, six CMS-backed case studies, a contact form and a password-protected draft case study. The following is a completed dependency decision based on official documentation, not observed contents of an exported ZIP.
| Assumed component | Expected export boundary | Completed migration decision |
|---|---|---|
| Static introduction and contact layout | Exportable page files and assets | Candidate for an external static implementation, still requiring a real rendering check |
| Six CMS-backed case studies | Content is not supplied as a working CMS in the code package | Hold migration until records are moved and pages rebuilt or rendered appropriately |
| Contact form | Submission handling needs another service | Do not call the exported contact route operational |
| Password-protected draft | Existing protection does not transfer | Exclude the draft from a public replacement until an appropriate access design is established |
Niko's completed decision is to keep the current hosted route while designing the replacement. The blockers concern the actual content and access model, not just a missing CSS file. No external site is marked ready and no Webflow plan is canceled in this exercise.
For the six records, Niko would retain titles, contribution text, evidence references and verification limits as separate migration inputs. Those fields preserve the contribution narrative for the replacement; importing them remains a separate task.
Exporting CMS records is a separate data task
The Collection import/export guide describes CSV exports separately from code export. It says rich text exports as HTML, while image and file fields can refer to Webflow-hosted URLs. Those references need attention if the original site is removed; a saved row is not necessarily an independent copy of every asset.
For Niko's proposed move, preserving six records would not by itself create six readable pages on another host. The destination still needs a content model or static rendering, working routes, permitted assets and accurate contribution text. This is why “I can export” and “I can replace the site” are different conclusions.
For a future migration, verify the reader-facing paths: inspect the resulting pages, relevant links and assets, then test the intended contact and access paths. Do not label the whole move successful based only on a downloaded data file. We downloaded neither a private CSV nor a code bundle.
Contact processing and ongoing costs remain your decision
Webflow's exported-forms guidance describes connecting a third-party form service or embedding another provider's form for an externally hosted site. That introduces another configuration, data destination and possibly another bill. Review those conditions before asking visitors to submit information.
A contact form's visible fields do not establish delivery, and a successful page load does not establish password protection. Choose the simplest appropriate contact route and collect only the information needed for a professional inquiry. No messages or form tests were sent for this review.
Webflow makes sense when its visual design and chosen content model justify the maintenance and plan costs. Compare recent roles on LandOffer.ai, decide which evidence belongs on the portfolio, and budget Site, Workspace, domain and any replacement services separately. Before migrating, identify and verify the content, contact and access functions the replacement must preserve.


