@fayazara introduces Screendrop, an open-source screenshot tool you can self-host

Announced in a brief X post amplified by Robert Scoble, Screendrop pitches open-source screenshots with self-hosting via R2 and a tiny hono worker.

By ยท Published

Why it matters

Open-source, self-hostable utilities are gaining favor with teams that want control over data and cost. If Screendrop is simple to run and integrate, it could become a go-to for capture and sharing without SaaS lock-in.

a minimalist, sculpted icon representing a screenshot utility (studio still life)

The X account @fayazara introduced Screendrop, an open-source screenshot tool, in a short post on X that was surfaced via a retweet from Robert Scoble (@Scobleizer). In the post, the author framed it simply: "Introducing Screendrop - a screenshot tool for everyone," adding "Opensource" and "Host your own cloud with R2 + a tiny little hono worker."

Robert Scoble on X

What got shipped

The announcement signals a developer-first approach: open source by default, with a do-it-yourself hosting model. The post name-checked "R2" and "a tiny little hono worker" but did not include a repository, website, demo, or setup guide. There is no public feature list in the materials we have, so it is not clear whether Screendrop targets desktop, browser, or mobile capture, or if it includes annotation, redaction, or sharing workflows.

Still, the intent is legible from the phrasing: a lightweight tool that anyone can run, with cloud storage you control and a minimal worker component to glue it together. For engineers and teams who prefer owning their workflow data, that framing is the appeal.

Founder-first thesis

The post reads like a builder shipping the smallest viable thing to invite early adopters. The emphasis on "for everyone" and self-hosting suggests a bet on portability and control over screenshots, rather than another proprietary silo. That approach has resonated with technical users in adjacent tooling categories, even if it asks a bit more from setup.

What we do not know yet

Because the post did not link out, several basics remain unspecified:

  • The canonical link for Screendrop (homepage and/or GitHub), including license and docs
  • Supported platforms (desktop app, browser extension, mobile) and core features beyond capture
  • Whether there is a hosted option in addition to self-hosting
  • How "R2 + a tiny little hono worker" is used in practice, and whether alternative backends are supported

If Screendrop ends up pairing simple capture with easy self-hosting and fast share links, it could slot neatly into developer workflows and internal documentation. For now, the teaser sets direction: open, small, and under your control.

Reader comments

Conversation for this story loads after sign-in.