Writing

The Screenshot Should Not Live Forever

4 min read

A closed laptop, a phone face down and a blurred print on a pale oak desk
The picture is the message. It does not need to live in three folders afterwards. Illustration.

The product at clipshot.io is called VanishShot now. It used to be called ClipShot. The domain stayed, because links people already sent should not die in a rename. The app is free for iPhone, iPad and Mac. There is no account and no subscription.

I built it for a narrow job. You have a screen, you need someone else to see exactly the part you mean, and you do not want that picture sitting in a chat log, a downloads folder and a camera roll for the next five years.

What it does, split by device

On iPhone and iPad you import a screenshot or any image through Apple’s private photo picker. VanishShot does not scan the photo library. You add arrows, rectangles, circles, lines, text and freehand marks, then export a full-resolution PNG or make a private link.

On Mac it is a menu-bar app. You capture a region, a window or the full screen, or you record the screen with audio. Then the same annotation, and the same choice: keep it on the machine, or make a link.

Nothing is uploaded until you choose Private Link. There is no analytics SDK and no advertising SDK in the app. A link can die after one view, after five views, or on a timer from five minutes to 30 days. Every uploaded clip is removed after 30 days at the latest, even if you picked a longer window than the file actually had. Anyone with the link can open it while it is alive. The token is long. Treat the link as the file.

Why a screenshot is a data-protection problem

Most of the screens I look at in a week contain something that should not be forwarded casually. A patient context that should never have been in the frame. A member list. A supplier invoice. A SharePoint permission dialog with real names. The default path makes that worse: the operating system writes a PNG to disk, a chat client uploads a second copy, and an agent transcript keeps a third if you paste the image into a coding tool to ask “what is wrong with this layout.”

VanishShot does not redact the picture for you. It does not understand what is sensitive. The control it offers is smaller and, I think, more honest. The file stays on the device unless you explicitly create a link, and the link is built to disappear. For a bug report, a design note or a support reply, disappearance is the correct retention period. “We might need it later” is how customer data accumulates in tools that were only meant to carry a message.

That is also why I do not position it as an AI product. People paste screenshots into agents all day. The agent is downstream. The decision that matters is whether a second system had to store the image in order for a person, or a model, to see it once.

The API is the same idea for a pipeline

There is a small HTTP API for the case where the screenshot is produced by a program rather than a thumb. One request uploads a file, up to 50 MB, and returns a private link.

curl https://clipshot.io/api/v1/clips \
  -H "Authorization: Bearer cs_live_..." \
  -F "[email protected]"

A CI job, a support tool or an internal app can hand someone a link that expires, instead of attaching the file to a ticket that lives forever. Documentation is at clipshot.io/developers. The Mac and iOS app is on the App Store as VanishShot.

What I left out on purpose

No workspace, no team folder, no “archive of all feedback.” Those features are how a private link becomes a document system, and a document system needs an owner, a retention schedule and an access model. VanishShot is the opposite bet: the message is the file, the file expires, and the next one starts from an empty state.

If you still have an old ClipShot link, it resolves on clipshot.io. That was the whole point of keeping the name on the domain and taking it off the icon.

Portrait of Håkon Berntsen

Written by

Håkon Berntsen

CTO and co-founder of Skjld Labs AS. Builds production AI agents, Microsoft 365 systems and the courses around them, from Sandefjord.

About LinkedIn GitHub