Pixelfed photos on any website.

Every Pixelfed user lives on a specific instance: a server running the open-source Pixelfed software (or a compatible alternative speaking the same ActivityPub protocol). Examples include pixelfed.social (the flagship instance run by the Pixelfed project), pixey.org (a popular general-purpose instance), pixelfed.de (German-speaking community), metapixl.com (photo-focused with stricter moderation), pix.bonk.land, pixelfed.au, and tens of thousands of smaller and self-hosted instances. A handle like @[email protected] tells the world your username and which server hosts your photos. Each instance has its own moderation rules, its own ActivityPub outbox at instance.tld/users/handle/outbox, its own hashtag index, and its own community norms. There is no central Pixelfed API to call. A widget that wants to embed a Pixelfed feed must resolve the instance from the handle and talk directly to that server. Poper does this automatically: paste any handle and the widget hits the right instance API, caches the response at our CDN edge, and renders photos with the same fidelity as the official Pixelfed web client, including multi-photo albums, alt text, and CW reveal overlays. The instance model has consequences for embed reliability that centralized platforms do not have. If pixelfed.social goes down for a maintenance window, your feed embedded from a different instance is unaffected. If a single small instance becomes unreachable, Poper's CDN cache continues to serve the last successful fetch so your portfolio page never breaks. And if your community runs its own Pixelfed instance for a niche like landscape, street, or analog film photography, that instance is a first-class citizen with the same widget support as the flagship server. Self-hosters get the same fidelity that pixelfed.social gets: no premium tier required, no exclusive integrations.

ActivityPub is the W3C-standard protocol that lets independent Fediverse servers talk to each other. Pixelfed and Mastodon both speak ActivityPub, so a follow from a Mastodon account to a Pixelfed account works seamlessly: the Mastodon user sees photos in their home timeline, can like and boost, and can leave replies that propagate back to the Pixelfed thread. This cross-platform federation is unique to the Fediverse and is one of the strongest reasons photographers choose Pixelfed over centralized alternatives. A film photographer with a Pixelfed account at @[email protected] can be followed by a journalist on @[email protected], an art curator on @[email protected], and a community on @[email protected] without any of those accounts ever creating a Pixelfed login. ActivityPub support extends beyond Mastodon and Pixelfed: Pleroma, Akkoma, Misskey, PeerTube (federated YouTube), Lemmy (federated Reddit), and even Threads (Meta announced ActivityPub support in 2024) all speak the same protocol. A Pixelfed feed widget that respects the protocol can pull from any of these without special-casing per platform. Poper renders ActivityPub Image and Note objects natively: photo attachments, multi-photo albums (Pixelfed calls these carousels), content warnings, custom emoji, alt text, and like and boost counts all come through correctly. For embeds, federation matters most for hashtag feeds: a tag like #filmphotography exists across many Pixelfed and Mastodon instances simultaneously, and the federated timeline aggregates them into a single visual wall. This is genuinely impossible on centralized photo platforms, where a hashtag is owned by one company and visible only inside that walled garden.

One of the deepest cultural differences between Pixelfed and Instagram is the absence of an algorithmic feed. Pixelfed shows you photos in reverse chronological order, exactly as they were posted, with no engagement-bait reordering, no sponsored injections, and no shadow banning. This is consequential for embedded feeds: when you embed a Pixelfed gallery on your portfolio or marketing site, your visitors see your most recent work first, every time. There is no risk that Pixelfed silently demotes a post because it links offsite, mentions a competitor, or includes a hashtag the algorithm dislikes. For brands fleeing Meta surveillance, this predictability is a major reason to migrate: what you publish is what your audience sees, in the order you published it. Poper preserves chronological order in every layout (Masonry, Grid, Carousel, Wall, Lightbox) and never reorders posts based on engagement. You can configure a custom hashtag-first or pinned-post-first ordering if your portfolio needs it, but the default matches the Pixelfed web client. The chronological order has practical SEO value too: a portfolio page whose newest photo is genuinely the newest gives Google a fresh-content signal every time you post, which is harder to engineer on an algorithmic platform that may decide to bury a post you wanted indexed. The combination of fresh, chronological photos, alt text captions that index as on-page copy, and ImageObject structured data per photo means an embedded Pixelfed gallery contributes meaningful SEO content to the host page rather than acting as an opaque iframe.

Pixelfed culture, inherited from broader Fediverse norms, treats content warnings (CWs) as a core social expectation rather than an afterthought. Photographers wrap potentially sensitive content (nudity in fine-art photography, blood in photojournalism, eye contact in street portraits, food, body, spoilers) with a CW so viewers can choose whether to reveal the photo. This consent-based approach is one reason post-Meta photographers find Pixelfed comfortable: the CW affordance gives viewers control that algorithmic feeds never offered. A Pixelfed widget that strips CWs (or worse, displays the wrapped photo without the warning) breaks this norm and damages the photographer's trust with their audience. Poper preserves CWs exactly: collapsed by default with a click-to-reveal overlay matching the Pixelfed web client, or always shown with a CW header if your portfolio prefers. You can also set a CW keyword filter to hide specific categories from your embed, useful for portfolios on professional sites where certain CW topics are off-topic. Alt text gets the same respectful treatment: rendered as a caption (the Pixelfed and Mastodon norm) rather than hidden in a tooltip. This matters for accessibility and for SEO: alt text is indexable, so a Pixelfed embed with rich alt captions adds genuine on-page content for search engines.

The default values of Pixelfed differ sharply from those of corporate photo platforms: no algorithmic feed, no engagement-bait amplification, no advertising, no data sale, no third-party tracking on embeds, and crucially no AI training on user content. The Pixelfed project has stated unambiguously that user photos will never be used to train generative AI models, a commitment that contrasts with Meta's 2024 disclosure that Instagram and Facebook public posts are scraped for Llama training, and with Adobe's controversial 2024 terms of service update around Creative Cloud. For photographers whose work is their livelihood, this difference is decisive: posting to Pixelfed does not feed a generative model that may later compete with you, replicate your style, or absorb your back catalog into a derivative dataset. A widget that breaks this privacy pattern by injecting cookies, tracking pixels, or fingerprinting libraries violates the platform's culture and gives privacy-aware visitors a reason to bounce. Poper ships a Pixelfed embed that respects these values: no cookies set by the widget, no tracking calls to third parties, no fingerprinting, no AI scrape pipeline, and a privacy policy that explicitly does not collect personal data from widget interactions. For GDPR-heavy sites (European media, photo agencies, journalism, fine-art galleries, museum and exhibition pages), this is a practical advantage: the embed does not trigger the cookie banner, does not require additional consent management, and does not appear in any data processing agreement audit. The post-Meta migration of 2023 to 2025 also brought a wave of professional photographers off Instagram after the Threads launch and the AI training disclosures. Many of those photographers landed on Pixelfed precisely because the platform refuses the surveillance economy that other photo apps depend on. A widget that mirrors that posture is a logical extension of the photographer's brand: open, federated, privacy-respecting, and chronological. Combine that with respect for content warnings, alt text, multi-photo carousels, and chronological order and the embed feels native to Pixelfed, not bolted on from a corporate social tool. For self-hosted Pixelfed admins, Poper's CDN cache also reduces load on the home instance: one fetch per cycle is shared across every visitor to every site embedding the feed, so a viral exhibition page does not translate into bandwidth pressure on the original server. That cooperative-with-the-instance behavior is another way the widget tries to align with Fediverse ethics rather than fight them.