To share a completed website made with OpenAI Codex, 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 temporary live URL. This is useful for a finished report, dashboard, prototype, or small static site that someone needs to open outside your coding environment.

This guide is for output that runs as static HTML in a browser. Build or export the finished static version first if the project needs a server, database, server-side rendering, or a private API; Dropley does not run those services.

For one self-contained page, ask Codex to save the entry page as exactly index.html. When the result uses local CSS, JavaScript, images, or fonts, keep the complete folder or ZIP and use relative references such as styles.css or images/chart.png. The HTML publishing guide and ZIP publishing guide are the canonical references for choosing the right upload and preserving its files.

In the project you want to publish, install the maintained Dropley skill:

1npx skills@latest add dropley/docs

Skills let Codex follow a reusable publishing workflow. If you do not use the skill, you can still upload the same index.html, folder, or ZIP on dropley.app. Publishing does not require an account.

Give Codex a specific request after the static files are ready:

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.

The resulting link is public and temporary. It is available for 1, 3, or 7 days, with 3 days as the default. Check the live URL before sharing it; see core concepts for the full artifact lifecycle.

Review the HTML, visible data, and local assets before publishing. Anyone with the resulting URL can open it until it expires, so do not use this workflow for content that needs authentication, private access control, permanent hosting, or a custom domain.

If the live page is missing styles, images, or scripts, verify that the complete folder or ZIP was included and the paths are relative. Use troubleshooting for failure checks and service limits for file, path, and expiry constraints.