1. LandOffer
  2. Blog
  3. All articles
  4. Self-Hosting a Carrd Portfolio: What Exports and What Needs Rebuilding?

Job search

Self-Hosting a Carrd Portfolio: What Exports and What Needs Rebuilding?

Distinguish downloaded source from working services, preserve your case studies and plan the next edit before sharing an independently hosted portfolio.

9 min readLandOffer team

Carrd offers a source-code download on Pro Plus or higher, but self-hosting requires more than opening the downloaded ZIP. The official instructions warn that platform-dependent elements, especially forms, can remain visible without working. Before using the independent portfolio in applications, open its case studies, inspect required assets, verify the contact behavior and make one later text revision.

This LandOffer guide checked official public documentation on October 22, 2026. We did not access a Carrd account, export an actual site, change DNS or deploy anything. We built a separate, original local-only static specimen to demonstrate a review method; it is not Carrd output. Choose the work relevant to recent technology roles on LandOffer before deciding which portfolio features need to survive a move.

A miniature planted greenhouse sits in an open transport crate beside a coiled hose and closed tool roll.

Check the export entitlement and the actual deliverable

The download documentation specifies Pro Plus or higher. It describes a ZIP containing unminified HTML, CSS and JavaScript, obtained through the site’s management controls. That is a source handoff, not a promise that all hosted services transfer with the layout.

The current plan comparison lists the base Pro Standard plan at $19 per year for ten sites and Pro Plus at $49 per year for twenty-five sites. Download Sites appears on Plus. The displayed annual difference is $30; that is not an account-specific upgrade invoice or the total cost of independent hosting. Check the applicable plan, remaining term and purchase quote before paying.

The documentation also says the downloaded version cannot be uploaded back into Carrd. Preserve the editable builder project separately if you may want to continue there. An independent source folder and a builder project have different editing paths; decide which will govern future changes rather than assuming a reversible round trip.

Inventory what the visitor must be able to do

Write down the visitor’s path: introduction, relevant case study, supporting evidence and intended contact route. Then list every feature that path depends on. Include fonts, images, external embeds, downloadable documents, navigation, forms and any restricted material.

A portfolio may need only static content and links. Another may depend on a scheduling widget, a private prototype or a submission service. The receiving host needs the required behavior, not just the appearance of the old element. A visible field and button do not establish a receiving endpoint or delivered message.

Use the inventory to protect the evidence a hiring reader needs while avoiding time spent recreating decorative features. A case study should explain the problem, your contribution, one decision and the evidence a reader can inspect. Preserve permitted original media and accurate captions. Retain scope labels such as “personal prototype” beside the project after the move. Changing the host does not change what work was performed.

Forms and embeds need their own replacement decision

Carrd’s contact-form guide describes a hosted feature that sends messages to the account email or selected recipients. The export warning means you cannot assume that a visually preserved contact form will keep doing that elsewhere. Choose an independently supported receiving service, replace the form with a suitable contact route, or remove it until the requirement is resolved.

For a public job-search portfolio, a clearly identified contact link may be enough. It has different privacy and spam implications from a form and does not need to pretend to collect structured submissions. If you require a form, specify where messages go, what data is collected, how abuse is handled and who checks that a submission arrived. Do not send a real message merely to investigate an undocumented export.

The custom-code guide allows HTML, CSS, JavaScript and third-party widgets. That capability does not establish that an external prototype, video, scheduler or script becomes an offline asset. Review each provider dependency separately. Keep the underlying case explanation readable even when an optional external demonstration is unavailable.

Preserve access boundaries and external assets

Carrd’s password instructions describe a Pro Plus publishing setting. They do not establish equivalent protection on your chosen independent host. Treat restricted material as excluded until you have an appropriate, separately verified access arrangement. A copied visual gate is not evidence that the underlying files are protected.

Fonts deserve an asset check as well. Carrd documents both external Google Fonts delivery and a serve-fonts-locally option. Inspect the actual files and references you retain. We did not test whether a specific Carrd download includes every font or media dependency, and the local specimen below deliberately uses system fonts.

For images and document attachments, open the retained destination rather than relying on a thumbnail. Open each required image or document at its retained path, compare filename capitalization and confirm that its caption identifies the intended version and permitted use. Keep an asset inventory and the original files you are entitled to retain. A working link to another service is a dependency, not proof that the file exists in your independent folder.

Worked specimen: a small portfolio you can inspect locally

To make the review concrete, we authored a three-page static specimen called Signal Trail. It is an invented design exercise about duplicate-event handling, with no real person, customer or professional outcome. Its original files are index.html, case-study.html, contact.html and styles.css; there is no Carrd export in this package.

The home page introduces one fictional case. The case page separates the problem, proposed contribution and limits: a written identifier-check and test-case exercise, with no implemented backend or measured reliability claim. The contact page explicitly removes the form and provides no mailbox or endpoint. It demonstrates an honest incomplete contact decision rather than a false working submission control.

We opened the specimen through the local server at desktop width 1,280 and mobile width 390. The observed review record was:

Check Actual local observation Limit of the observation
Home to case study The named case-study link opened the intended page using Enter Proves this specimen’s link, not a Carrd export path
Case to contact page The contact-replacement link opened its explanation No message can be sent and no receiving service was tested
Return to home The return link opened the original index No domain redirect or public route was configured
Content width All three pages stayed within both tested viewport widths Not a full accessibility or every-device certification
Page structure Each page contained one main heading Does not establish the accuracy of a real work sample
Service dependency No form elements or scripts were present in the specimen Does not inspect another portfolio’s external dependencies

The finished specimen review note reads: “The local reading path works from home to case to contact explanation and back. The design exercise’s limits remain visible. There is no submission form to mistake for a working service. Public hosting, TLS, domain configuration, a real contact method and any actual Carrd-export fidelity remain untested.”

The original specimen’s links and tested layouts worked locally. This observation is limited to those four authored files at the two inspected viewport widths. It shows how to inspect the reader’s path after removing a dependency. It does not establish that a different site will export correctly, that its private pages remain protected, or that a production migration has been completed.

A brass watering manifold and disconnected hose rest on a potting bench in front of a small greenhouse.

Worked handoff: turn a ZIP request into a complete brief

Tessa is a separate fictional portfolio owner considering an independent copy of two public case studies. Her proposed source includes a contact form, an external prototype and one restricted draft. No account, real export or private material is involved. She completes this handoff record before asking anyone to move the site.

Component Completed handoff choice Evidence still required for release
Two public case studies Preserve approved narrative, contribution labels and original diagrams Open both case destinations and compare the full content
Contact form Remove from the first independent version Confirm that no visible submission control suggests it still works
External prototype Keep an optional link with a plain-text explanation Check provider access and retain the explanation if access fails
Restricted draft Exclude entirely from the public copy Review actual retained files, not only navigation menus
Fonts and media Inventory local files and external references separately Inspect rendering and each required destination on the receiving host
Future edits Keep one named source folder and a dated release copy Make one later text correction and reproduce the revised output

Her complete brief reads: “Deliver the two approved public cases with their original diagrams and accurate scope statements. Remove the form and excluded draft. Identify any external prototype or font reference. Supply editable source, a file inventory and instructions for the next text change. Preserve the Carrd project separately. Do not describe the ZIP, a screenshot or a successful home-page load as a completed migration.”

Her release memo is: “The reduced scope is defined; independent hosting is not verified. Before changing the existing domain, check both cases, media, navigation and the removed-form state on the intended host. Confirm the actual access arrangement for anything restricted. Keep the original site available until the replacement and update process meet the agreed checks.”

Tessa’s decision is to proceed only with the reduced public handoff. She has removed unnecessary service requirements from the first version while retaining explicit checks for the remaining dependencies. The exercise supplies a completed brief and decision, not a claim that files were exported or a host passed them.

Domain, TLS and the next update remain separate work

Carrd’s custom-domain guide describes registering a domain separately and pointing its records to Carrd. A new host requires its own domain and secure-delivery setup. Do not copy the old target into a migration brief and assume it now points to the replacement. We made no domain or hosting changes.

Review the exact addresses already included in resumes and applications. An independent copy may use different file paths or section anchors. Keep a mapping of important old destinations and their intended replacements, then check the actual destination after an authorized release. A home page that opens does not settle every case-study link.

Name the authoritative editing source after the move. If you continue editing in Carrd and downloading later copies, document how independent changes will be reconciled. If you switch to hand-maintained files, preserve the content and asset organization needed for the next revision. Carrd’s no-reupload limitation makes that choice consequential.

Budget for recurring maintenance as well as a one-time transfer: reviewing dependencies, renewing services, correcting content and retaining backups. Hosting charges, domain renewal and any replacement submission provider are separate from the Carrd plan price. This guide does not assume a free host, guaranteed uptime or a fixed migration cost.

Decide when an independent copy is ready

Close the task against the visitor path and the handoff record. Open every required case, inspect its media, verify the intended contact behavior, check excluded material and record where the editable source and backup live. Test the next small revision while the source project is still available.

For a portfolio supporting applications, use recent roles on LandOffer to select the case that explains the employer’s requested work. Preserve the exact URL and reviewed version in your application record. Keep a completed check record for the reading path, contact behavior, excluded files and next revision. Leave any untested host, domain or receiving service explicitly unresolved before sharing the replacement address.

Sources and Further Reading