Context
Add the purpose, audience, and question that are easy to lose when a project is viewed only as an isolated pen.
Limited-time offerPro & Max plans — 20% offSave 20% on monthly and yearly billing.
Save 20% on monthly and yearly billing.
For a complete front-end page
CodePen 2.0 can deploy a Pen to a CodePen website, and its export flow can produce downloadable project files. When you need a separate, replaceable review copy of the browser-ready export, HTMLShare can publish those static files as a normal preview; it does not sync with CodePen or replace its editor and community features.
Static export contract
A complete-page preview is useful when the audience should assess the result rather than edit the Pen.
Add the purpose, audience, and question that are easy to lose when a project is viewed only as an isolated pen.
Inspect the exported ZIP and use its browser-ready dist output, including index.html and the local CSS, JavaScript, images, and fonts the page needs.
Let a client, teammate, or product owner open the page without an editor frame or development setup.
Where the export helps
Send a complete interaction or landing page concept to a client who needs to review the experience, not remix the code.
Turn a front-end experiment into a focused case or project page while you decide how it belongs in your portfolio.
Give product or engineering a stable snapshot of the result before the experiment becomes a larger project.
Why this handoff works
The reviewer opens the output as a page, which is often clearer for clients and non-developers than an embedded editor.
ZIP upload keeps local CSS, JavaScript, images, and fonts together when the export is more than a snippet.
Use CodePen 2.0 when its deployed Pen, versioning, or collaboration workflow is the right destination. Use HTMLShare for a focused, replaceable review copy when that is the next job.
A three-step workflow
Use CodePen's Export menu, download the ZIP, and identify the browser-ready dist output and its HTML entry point.
Upload the dist contents as a self-contained HTML page or create a ZIP with index.html, CSS, JavaScript, images, fonts, and relative paths.
Open the page yourself, check the interaction and responsive layout, then send the URL with a clear review question.
Know the boundary
HTMLShare publishes browser-ready static output. Keep builds, source tools, private access, live data, and production operations in the systems built for them.
HTMLShare does not import Pens, sync edits, preserve CodePen community metadata, or provide an embedded CodePen editor.
CodePen exports can keep external resources as remote links. Package local assets when the review needs a stable snapshot, and test any remaining external dependency.
Use production hosting when the page needs a permanent public URL, analytics, forms, backend behavior, or long-term operations.
Keep exploring
Compare the two review experiences.
Open pageShare interactive HTML with clients.
Open pageKeep the export complete.
Open pageGive the work a considered frame.
Open pageCheck the current export layout and resource caveats.
Open pageBefore you publish
Use CodePen's Export menu to download the ZIP, identify the browser-ready dist output, then upload that HTML or a ZIP with index.html and its local assets to HTMLShare.
No. HTMLShare publishes the exported snapshot. Make changes in CodePen or your source workflow, export again, and create a new review copy when needed.
Use CodePen when its editor, deployed Pen, versioning, or collaboration features are part of the review. Use HTMLShare when the client should open a complete exported page without an editor-oriented context.
Ready for the next review
Create a noindex preview link for the static HTML or ZIP project, then move approved work to production when it is ready.