Check the current transition notice
Anthropic says the standalone Claude Design site closes on December 14, 2026, with the standalone version becoming read-only. Project migration is rolling out to paid plans, so the controls available to you can differ. Read the current migration notice before acting; this guide was checked on November 4, 2026.
The important distinction is between a native project you can continue editing and a file you can keep independently. Prepare both where the product permits them. Do not delete the old work as a way to test whether the move succeeded.
Keep an archive and a reading copy
For a standalone project, Anthropic documents Share → Project HTML → Project archive → Export for a ZIP containing the project files. In a slide deck, Project HTML is under More formats and apps. Preserve the complete archive before extracting a separate working copy. Download instructions
Then choose the format your reviewer needs. Claude Design’s export guide lists ZIP, PDF, PPTX, and standalone HTML among its options. Use HTML when browser interactions matter, PDF for a fixed reading copy, or the requested presentation format. One export is not proof that every other format is complete.
Here is an original fictional reading copy for a bakery concept review. You can change the selected concept and see its rationale. It contains no Claude project data and does not demonstrate that native migration has run. It shows the kind of independent review page you can test after export.
Open the review copy · Open its HTML file
Capture decisions that are outside the design
The migration notice says chats and comments stay in the standalone version. Before the transition, record the decisions you need from them in a document your team can access. Include the design revision, the decision, who must confirm it, and any open question. Mark a proposal as a proposal; a comment suggesting a color is not an approval.
For the bakery example, a useful note is: “Round 2 compares Sunroom and Hearth. The owner has not approved either. Confirm the sign color before production.” A screenshot of a chosen tab would not preserve that unresolved decision.
Verify the move before resuming work
When your account offers project migration, review its stated changes and keep the tab open until it finishes. Moving makes the standalone copy read-only and cannot be undone according to Anthropic’s notice. The project owner should review that consequence before confirming.
Open the resulting project in Claude, compare its content with the original, and test the controls your reviewer will use. Separately inspect sharing. Current artifact sharing controls vary by plan and organization policy; do not assume every old link, invitation, or access level behaves identically after a transition.
For an HTML export, open the file away from its extracted folder and check its images and interactions. If that fails, keep the archive intact and inspect the missing dependencies. The compatibility guide covers that file-level check.
Ask for a handover note without inventing approvals
Prepare a handover note for this design transition.
Project and source revision: [ENTER].
Design files and permitted decision notes: [ATTACH].
Required deliverables: [NATIVE PROJECT / HTML / PDF / PPTX].
List the design content, confirmed decisions, unresolved comments,
and sharing settings we need to verify. Keep the original wording
of approvals and do not infer consent from a selected concept.
Identify anything the export cannot preserve. Create an independent
HTML review copy only if the supplied content is enough; label it
as a snapshot, not a migrated project. No external assets or fake
submission controls. State what has and has not actually been tested.
Keep the right place for continued work
Continue native editing and collaboration in Claude when that is the required workflow. Keep the archive as the source backup and a checked reading copy for handover. For a small standalone HTML page you want to distribute as a browser link, the NOS handoff guide covers that additional step.
A NOS page is not a backup of Claude conversations, comments, permissions, or connected services. Keep those requirements in the transition checklist, rather than treating a good-looking preview as evidence that the project is safe.