You sent someone a link on Monday. By Thursday the work has moved on, and on most hosts that means a fresh upload, a fresh URL, and an email that starts with 'ignore my last one'. Three revisions in, your client is holding four links and no idea which is live. It doesn't have to work that way: replace the contents at the same address instead. The password stays, the expiry stays, every version is kept, and the URL in their bookmark quietly becomes correct again.
Try it now
Drop a file — get a private link in seconds. No sign-up.
Drop an HTML file or ZIP bundle, or click to choose.
Single file or ZIP. Max 3 MB.
Up to 3 MB, link self-destructs after 7 days. Sign up free to keep links forever, password-protect them, and store more.
Publish once and send that link — from the web uploader, from the CLI, or from an AI assistant over the MCP connector. That URL is now the address of the work, not a snapshot of one draft of it.
When the work changes, replace the contents rather than uploading a new file. The link is untouched, and so are the settings attached to it: a password you set still applies, an expiry date still counts down to the same day, the title in your dashboard stays put. Each replacement is stored as a numbered version, so 'always current' doesn't mean losing what came before.
Everyone holding the link sees the new version the next time they open it. Nothing to re-send, nothing to announce, no dead URLs accumulating in someone's inbox. If an AI assistant is doing the iterating, it can perform the replacement itself, so the live link never drifts behind the actual work.
Because they're designed for publishing rather than delivering. In a publishing model each upload is a distinct release, and keeping the previous one reachable at its own address is the correct behaviour — that's what you want for versioned releases of a public site. Delivery has the opposite requirement: one stable address for 'the current state of the thing I'm making for you', held for weeks. Neither design is wrong, they're just answering different questions. This is the second one.
No — that's the whole point of a replacement being different from a new upload. The password stays, so people who were let in are still let in and nobody else is. The expiry keeps counting to the date you originally set rather than restarting. The title and the project it's filed under stay as they were. You're changing the contents, not re-creating the page.
Each replacement is kept as a numbered version rather than overwriting the last one, so the history is there rather than discarded. If you need a specific state to stay citable — the version a client approved, something attached to an invoice — the cleaner move is to publish that one separately so it stops moving, and keep the working link for the work. A live link is deliberately always-current, which makes it a poor archival record by design.
Yes, over the MCP connector — it can replace the contents of a page it published earlier, keeping the same link. This matters more than it sounds: without it, the loop ends with a file on your disk and a small chore attached, and small chores get skipped when you're busy. Skipped chores are how a live link drifts behind the real work, which is the exact failure this is meant to prevent. Note the connector carries HTML as text with a practical ceiling near 100 KB; larger files go via the CLI or uploader, same link either way.
Then set an expiry, or change the password so anyone holding the old one is out. Both are reversible decisions you can make at any point. Replacing contents and revoking access are separate controls here on purpose — revoking shouldn't require destroying the page, and updating shouldn't require issuing a new URL.
Replacing contents at the same link works on every plan. The thing to watch on free is expiry: those links self-destruct after 7 days, which undercuts the point if you're planning to iterate against the same URL for a month. Solo ($4.99/mo) and up have links that never expire unless you choose to set one, which is what a long-lived delivery link needs.
No card to try, no sign-up to get a link. Sign up free to keep links forever, password-protect them, and store more.