Introducing Snipe.pics: Federated Image Sharing, Built the Right Way
Snipe Group Limited is today announcing the full launch of Snipe.pics, a federated image-sharing platform built on Pixelfed and the ActivityPub protocol. It is the latest service to join the SnipeSearch Fediverse ecosystem, an infrastructure that has been expanding steadily since our Mastodon instance launched in November 2022, and that now spans social networking, federated video, and image hosting across servers in four countries.
This post sets out what Snipe.pics is, how it fits within the broader ecosystem, and why the architectural decisions we have made matter for anyone who cares about where image sharing on the open web is heading.
The Problem with Centralised Image Platforms
The dominant image-sharing platforms of the last fifteen years share a common architecture: a single corporation controls the infrastructure, owns the relationship with every user, and monetises that relationship through behavioural data harvesting. Your followers, your posting history, your engagement, none of it belongs to you in any portable or transferable sense. It belongs to the platform. If the platform changes its algorithm, restricts your reach, alters its terms of service, or simply closes, you have no recourse and no exit with your audience intact.
This is not an accident of design. It is the design. Lock-in is the product.
SnipeSearch was founded in 2005 on a direct rejection of that model in the context of search. The same principle has governed every service we have built since: users should own their data, their identity, and their audience. No platform we operate tracks user behaviour for commercial purposes, profiles its users, or sells data to third parties. That commitment predates the regulatory frameworks that have since made such practices legally contentious. It has always been our position, not a compliance response.
Snipe.pics applies that same position to image sharing.
What Snipe.pics Is
Snipe.pics is a Pixelfed instance, a deployment of the open-source, federated image platform built on ActivityPub, the same protocol that underlies Mastodon, Friendica, PeerTube, and the wider network known as the Fediverse. The platform is live now at snipe.pics.
The distinction between a Pixelfed instance and a conventional image platform is architectural, and it is significant. Content published on Snipe.pics does not exist in a closed system. It is immediately visible and interactable from any ActivityPub-compatible server on the Fediverse. A user on mastodon.social or pixelfed.social can follow a Snipe.pics account, engage with its posts, and receive updates in their home feed without holding a Snipe.pics account. Federation with pixelfed.social, friendica.world, bookwyrm, and peertube is confirmed active.
The homepage positions this as “one account, the whole open web”, which is an accurate description of how ActivityPub federation works in practice. Your presence on Snipe.pics is not bounded by Snipe.pics.
Features and Capability
Snipe.pics offers the full feature set expected of a production Pixelfed deployment. Users can upload high-quality photos up to 15MB, compile albums of up to four images per post, and publish ephemeral content via Stories and Moments. Privacy controls operate at the individual post level. Image derivatives are optimised automatically for every screen size and resolution. The platform supports the open mobile API, meaning compatibility with established third-party Fediverse applications from day one.
Full account portability is supported and treated as a non-negotiable property of the platform. Users can migrate their followers, content, and identity to any other ActivityPub-compatible server. This is a capability that centralised platforms cannot offer by design, the portability of your audience is incompatible with the lock-in model that makes those platforms commercially viable. On Snipe.pics, portability is a feature, not a threat.
Integration with the SnipeSearch Ecosystem
Snipe.pics integrates directly with SnipeSocial, the SnipeSearch social network that has been in continuous operation since 2016, via OAuth single sign-on. Users with an existing SnipeSocial account can authenticate to Snipe.pics in a single step with no separate registration required. Their SnipeSocial credentials function as a verified identity across both services.
This reflects a deliberate infrastructure philosophy: one verified identity, working across multiple federated services, owned and controlled by the user rather than by any individual platform. As the ecosystem expands, that identity layer becomes more valuable, not less, and it remains entirely in the user’s hands.
Snipe.pics sits alongside the SnipeSearch Mastodon instance, SnipeSocial, and the wider suite of services that constitute the Snipe Group ecosystem. Infrastructure supporting these services runs across servers in Hertfordshire, Netherlands, Czech Republic, France, and Thailand, with company offices in London, Borehamwood, Brno, and Phuket.
Privacy and Monetisation
The platform’s cookie notice is displayed at the point of user contact and states explicitly: “We use an essential login cookie to keep you signed in, plus non-tracking advertising cookies from a-ads and Snipesearch AdClicks. No third-party tracking, no profiling, no data sale.” Both advertising providers are named. The commitment is stated plainly, not buried in supplementary documentation.
Contextual, non-tracking advertising has funded SnipeSocial’s infrastructure since 2015. It is the model we have chosen not as a compromise but as a considered position: contextual advertising is compatible with genuine user privacy, has a decades-long track record of funding independent publishing, and is demonstrably more sustainable than the volunteer-dependency model that has caused a significant proportion of Fediverse instances to go dark or reduce capacity over the same period.
Research tracking over 21,000 Fediverse instances as of 2024 found approximately 24 percent completely offline and 58 percent dormant. High-profile collapses, including the flagship Diaspora pod JoinDiaspora.com, the peertube.video instance, and mastodon.technology, have each been attributed to the same underlying cause: infrastructure costs and administrative burden that volunteerism alone cannot sustain at scale. Snipe.pics has been designed from the outset with a monetisation model that keeps the lights on without compromising the privacy commitments that justify its existence.
What Comes Next
Snipe.pics represents the latest stage of an ecosystem that has been in continuous development since 2005. Snipe Group Limited was incorporated in April 2026, Company No. 17158391, after twenty-one years of operating SnipeSearch and its associated services as an independent entity. The formal incorporation marks a new phase for the group, and Snipe.pics is the first significant service launch under that structure.
The @snipesearch account on Snipe.pics is active. Federation is live. The infrastructure is in place and operating across four countries. We will continue to develop the platform and the broader ecosystem — Snipe.pics is not the last service this network will add to the Fediverse.
We are confident it represents the right approach to image sharing on the open web, and we invite anyone who shares that view to join us.
Snipe.pics is available now at snipe.pics.
Follow the SnipeSearch ecosystem account at @snipesearch from any Fediverse-compatible platform.
— Stephen Driver
Co-Founder, Snipe Group Limited
