To share a completed Claude Code HTML artifact outside Claude, save its static output as index.html (or as a folder or ZIP when it has local files), publish it to Dropley, and send the resulting live URL. This is useful when you need a standalone, temporary link for a finished static page such as a report, dashboard, or prototype.

This guide is for output that can run as static HTML in a browser. It is not a replacement for Claude's own Artifact publishing: use Claude's native sharing when you want the artifact to stay in Claude. Use Dropley only after you have a completed static file or project you intend to share publicly.

For a one-file page, ask Claude Code to save the finished result as index.html. For a multi-file result, keep the complete folder structure and use relative references such as styles.css, scripts/app.js, and images/chart.png. See how to share an HTML file online and how to publish a ZIP static website for the full upload requirements.

If you use the Dropley skill with Claude Code, install it in your project first:

1npx skills@latest add dropley/docs

Then give Claude Code a specific publishing request. If you are not using the skill, upload the same index.html, folder, or ZIP yourself in the browser.

123Create a finished static project for this dashboard. Save the entry page as
index.html, keep local assets in relative paths, and do not use server-side code.
Publish the completed project to Dropley and return the shareable URL.

Dropley links are temporary—available for 1, 3, or 7 days, with 3 days as the default—so open the URL once before you send it and upload again if you need a new link later. See core concepts for the artifact lifecycle.

Review the HTML, visible data, and local assets before publishing. The generated Dropley URL is a public share link, so anyone you send it to can open it until it expires. Do not use this workflow for content that needs authentication, private access control, permanent hosting, or a custom domain.

If the page is missing styles, images, or scripts after publishing, confirm that you uploaded the complete folder or ZIP and that its paths are relative. The troubleshooting guide covers common upload and serving problems; service limits lists file, path, and expiry constraints.