Inspect the failing part first
Open the exported copy and name the first reproducible failure. “Blank after clicking Calculate” is useful. “Export is broken” leaves too many possibilities open.
Then inspect the delivered files. Is there a complete HTML document? Does it reference a separate image, stylesheet, or JavaScript file? Is the downloaded source a React component that needs a build, rather than a finished browser document? Do not rename a component to .html and treat that as an export.
For an initial source check, search for these patterns. They are clues, not a complete audit:
src=" href=" fetch(
import /api/ localhost
window.claude window.storage process.env
An inline SVG and a local event handler can belong to a standalone page. A call to a platform API or a server endpoint needs a separate explanation. Do not paste credentials into the file to make such a call “portable.”
Test a small standalone copy
This original fictional estimate has two package variants. Switching from Essential to Extended changes the displayed price from $480 to $720. A second button confirms the current choice on screen only. Both functions run in the HTML file, with no network request and no persistence.
Open the working fixture · Open the complete HTML
Copy the HTML into a new folder by itself and test both variants. Close it and open it again: the initial variant returns because this example does not save a choice. That is expected behavior, stated beside the controls. Your own export should be equally explicit about what survives a reload.
Separate appearance from platform features
Anthropic’s artifact documentation describes artifacts that use Claude, connect to apps, and store data. Those features depend on more than the visible page. Copying its interface into HTML does not itself reproduce the underlying service.
For each important control, write its actual job:
- Change a tab, filter embedded data, or calculate from supplied inputs: implement and test it in the browser copy.
- Ask Claude a new question: retain the native artifact or build an appropriately authenticated application.
- Read a connected workspace or save shared records: retain the required account, permissions, storage, and server behavior.
The native route may be the simpler answer for an artifact that needs those capabilities. Check its sharing settings for the intended audience. A standalone snapshot can be useful for review, but label it as a snapshot and remove or explain controls that cannot work there.
Request the exact export you need
This prompt asks for a deliberate standalone version rather than a promise that everything will transfer:
Prepare a standalone review copy of this artifact for [AUDIENCE].
Required behavior: [LIST EACH CONTROL AND EXPECTED RESULT].
Permitted snapshot data: [SUPPLY].
First identify dependencies: separate files, packages, Claude calls,
connectors, storage, environment variables, and server endpoints.
Distinguish browser-only features from features requiring a service.
For the review copy, return one complete HTML file with inline CSS
and JavaScript and embedded or inline assets. Use only supplied data.
Preserve [LIST]. Remove or clearly label unavailable live features.
Do not replace a real submission with an unlabeled success message.
No secrets, remote dependencies, fake saved state, or claimed tests.
Include expected checks for initial state, interaction, and reload.
Verify the exported behavior, not a similar preview
Open the actual delivered file at phone width. Test an initial result, a changed input, an empty input if one is allowed, and a reload. If your page calculates a price, check a boundary value. If it displays a source snapshot, compare a record against that source.
Record whether you tested locally or behind the final browser link. A script that works in one environment may encounter different restrictions in another. The example in this guide is authored for the article; it is not evidence that a native Claude export or a connected application was migrated successfully.
Choose a host after deciding what must run
Use application hosting when the result needs its own backend. For a self-contained review page, NOS’s HTML-to-link guide describes how to turn the reviewed HTML into a reading link. Check the recipient’s page and its required interactions before sending it.
NOS does not supply Claude’s connected apps, native AI execution, or artifact storage. Keeping that boundary clear saves you from moving the same incomplete interface between hosts while its missing dependency remains unresolved.