Export options available
Marcus gives you two ways to export your code. The first is a static ZIP download — click the export button in your project dashboard and you'll get a complete archive of all files. The second is pushing to a private Git repository on GitHub, GitLab, or Bitbucket, which lets you version-control changes and deploy via standard CI/CD pipelines.
Both options are available on all paid plans. The free tier lets you export projects up to 5 pages. There's no lock-in period or export quota — download as many times as you need while your subscription is active.
What's inside the export
The ZIP contains a fully self-contained website. You'll find an index.html and additional HTML files for each page, a /css folder with stylesheets (including the design tokens Marcus generated for your brand), a /js folder with any interactive components, and an /assets folder with images and fonts.
Everything is organized in a standard web project structure. No proprietary formats, no obfuscation. If you know HTML and CSS, you can read and modify every file. The code uses semantic markup, CSS custom properties for theming, and vanilla JavaScript where interactivity is needed — no framework lock-in unless you specifically asked Marcus to use one.
No Marcus runtime needed
For static sites — marketing pages, portfolios, documentation, landing pages — the exported code runs entirely in the browser. Upload the files to Netlify, Vercel, Cloudflare Pages, or any web host that serves HTML, and it works. No build step required, no server dependencies, no Marcus account needed to keep the site online.
This is possible because Marcus generates static HTML at export time. The pages you see in the Marcus editor are the same pages in the ZIP. There's no rendering engine to deploy, no API calls back to Marcus servers once the site is live.
Projects with backend features
If you're building a SaaS app or any project that needs user authentication, database storage, or payment processing, the export includes scaffolding code for those features. You'll get Node.js or Python backend files (depending on what you chose), environment variable templates, and integration code for Stripe billing and auth providers.
These exports are not fully runnable without additional setup. You'll need to configure your own database, add your Stripe API keys, and deploy the backend to a service like Railway, Render, or Fly.io. Marcus doesn't host dynamic backends — the export gives you a working foundation that you wire up to your own infrastructure.
The auth and billing code is production-ready scaffolding, not a complete application. Think of it as a well-structured starting point that handles the repetitive parts — session management, password hashing, webhook verification — so you can focus on your product's unique logic.
Using Git export for ongoing development
The Git export option creates a new repository under your account and pushes Marcus's latest code to it. After the initial push, you can pull the repo locally, make changes in your own editor, and commit them. If you ask Marcus to make further edits, it can push updates to a new branch so you can review and merge them without overwriting your custom work.
This workflow makes sense if you're using Marcus to build the foundation and plan to extend it with a development team. The Git history shows exactly what Marcus generated, and your commits show what you changed. You're not tied to the Marcus editor once you have the code — it's yours to maintain however you prefer.
Who owns the exported code
You do. The code Marcus generates for your project is yours to use commercially, modify, or redistribute. There are no royalties, no attribution requirements, and no restrictions on what you build with it. The only limitation is that you can't resell Marcus-generated templates as a competing website builder product.
This applies to both the Builder plan (€29/project/month) and the Studio plan (€290/month for up to 25 projects). The free tier has the same ownership terms — you own the code for your one project and five pages, even if you later cancel.
When to care about export
Export matters if you're building a long-term business asset and want the option to move off Marcus later. It matters if you need to hand the project to a developer who doesn't use Marcus. And it matters if your organization requires all code to be stored in internal Git repositories for compliance or audit reasons.
For simple static sites where you're happy with the Marcus editor and hosting, you might never export. The option exists so you're never locked in — not because you're expected to leave, but because knowing you can leave makes it easier to commit.