Turn the HTML your AI made into a live link

When Claude builds a page, it shows it as an artifact next to the chat. Open the artifact and use its copy or download option to get the code, then save it as a file ending in .html (for example index.html). Check which kind of artifact you have. An HTML artifact is ready to upload as it is. A React artifact is a component, not a page, so it will not run on its own; ask Claude to "rewrite this as one self-contained HTML file with the CSS and JavaScript inline, loading any libraries from a CDN" and save that version. Then drag the .html onto the uploader, sign in, and copy your link. If you use Claude Code instead of the chat, the file is already on your disk, and with our MCP server connected Claude can publish it and hand you the link in the same conversation.

ChatGPT and Gemini can both write and preview web pages in a side panel. The simplest reliable route is the same for both: copy the full code, paste it into a plain text editor (Notepad, TextEdit in plain-text mode, VS Code), and save it as index.html. Before you copy, ask the assistant to "put everything in a single HTML file", because answers sometimes split the CSS and JavaScript into separate blocks, and a lone .html cannot load files that sit next to it. Images work when they point to full https:// addresses or are embedded as data URIs. Open the saved file in your own browser once; if it looks right there, it will look right at the link. Upload it, and the person you send it to gets the working page, with no ChatGPT or Gemini account needed to view it.

App builders such as Lovable and Bolt generate a full front-end project, typically React with Vite, rather than one HTML file. Uploading the source will not work, because the browser needs the built output. Get the code out first: sync the project to GitHub or download it, depending on what your tool offers. Then, on your computer, run npm install and npm run build. That creates a dist/ folder with an index.html and the bundled JavaScript and CSS. Zip that folder and publish it with website hosting, which needs Pro: we find the index.html, serve every asset with the right type, and can fall back to index.html for client-side routes so refreshes and deep links work. If the app talks to a hosted backend such as Supabase from the browser, those HTTPS calls keep working, as long as that service accepts requests and sign-in redirects from your new address, so add the new URL to its allowed list.

v0 usually generates React components built for Next.js. You have two honest options. For a quick mockup or a landing page you only want people to look at, ask v0 for "a single static HTML file using Tailwind from a CDN", save it as index.html, and upload it as a normal link. For a real app, download the code and run it locally. If the app has no server features, set output: 'export' in next.config, run the build, and Next.js writes a static out/ folder you can zip and publish as a website on Pro. If it relies on API routes, server actions or per-request rendering, it needs a platform that runs a Node server, and static hosting is the wrong fit; we would rather tell you that than take the upload.

Coding agents write real files, so there is nothing to copy out. A single report.html or demo.html in your project can be dragged onto the uploader as it is. A project with a build step works like Lovable: run the build and publish the output folder as a ZIP website on Pro. The faster path is our MCP server. Add it to Claude Code with one command, or to Cursor and VS Code through their MCP config, using an API key from your dashboard. Then ask the agent to "build a one-page summary of this data as HTML and publish it as a link", and it uploads the file through the same checks as the website and replies with the URL. The agent cannot change link settings or delete links; you keep that control in the dashboard.

Count the files. If everything lives in one .html (styles in a <style> tag, scripts in a <script> tag, libraries from a CDN), publish it as a normal link: it works on every plan, up to 250 MB per file on Free and 500 MB on Pro, and it gets the full set of link controls, including a QR code, view analytics, a password, an expiry date and your own domain. If the page needs other files next to it (a second page, a /assets folder, a JavaScript bundle), it is a website, so zip the folder and publish it with website hosting on Pro. Either way, replacing the file or re-uploading the ZIP keeps the same link, so when the AI gives you a better version next week, nobody needs a new URL.