Delete a shared image when you are done with it

Shared links are unlisted, not secret. They are not guessable and not indexed by search engines, but if you post the URL somewhere public, or if the person you sent it to forwards it onward, the image is reachable by anyone who has the string. The delete button is how you close that loop when the image has outlived its usefulness.

Where the delete button lives

Open the share URL in any browser. The image renders on the left; the share controls sit on the right — the URL, the Copy link button, and a Download button. The delete control lives on the same page, typically under the URL row. Click it, confirm the prompt, and the request fires off to storage.

What actually happens when you delete

1. The delete request goes to the imagepaste edge API.
2. The R2 storage entry is removed within about a minute.
3. The share URL starts returning a 404 response on the next fetch.
4. The 12-character ID is retired — it is never reused for a future upload.

Cached copies matter. If the image was hot-linked into a Slack message, a forum post, or a blog, those viewers may see a cached version for a few minutes until their CDN or browser cache expires. Usually this is 5–10 minutes. After that, all requests hit the 404.

Deletion is permanent. There is no trash, no undo, and no second copy on the server.

What if I lost the share page?

The share URL is the only handle for a specific upload. There is no account, no dashboard, and no history list tied to your identity. The site cannot see a list of your uploads, because it does not know who "you" are.

In practice, the share link lives in three places:

• Your browser history for the session. Search it for "imagepaste".
• Wherever you pasted the link — Slack, the ticket, the email thread.
• Your clipboard manager, if you use one. Raycast, Maccy, and Clipy on macOS all keep the last N clipboard entries.

If all three are gone, the upload is stuck at whatever random ID it was assigned. It will still not be indexed, still not be guessable, and still only be reachable by someone who has the exact 12-character string. But it will also not be deletable until you find that string again.

Preventing the problem

Two low-effort habits make this a non-issue:

1. Bookmark the share page for anything you might want to delete later. A single bookmarks folder called "uploads" covers it.
2. Keep the delete tab open for high-stakes uploads (a dashboard with customer data, a screenshot from a paid-for app). Close it only after you have confirmed the recipient has what they need.

Rate limits on deletion

There is no special limit on deletions — they go through the same edge as regular API calls. If you paste a link and want to remove it immediately, that works. The only caveat is that cache warmup can mean the image is briefly visible at a CDN node after the storage delete has completed. For sensitive uploads, wait the few minutes for cache TTL before assuming the image is truly gone.

Tutorials that go with this one

The Ctrl+V paste guide and the crop guide cover the upload side. The mobile guide covers the phone flow. Delete is always the same regardless of how the upload was created.