Pixelfed photos on your 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 many smaller and self-hosted instances. A profile URL tells the widget which server hosts the photos. Each instance has its own moderation rules, its own ActivityPub outbox at instance.tld/users/handle/outbox, 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 profile ID or URL and talk directly to that server. Poper does this automatically: paste a profile ID or full profile URL 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 a single small instance becomes unreachable, Poper's CDN cache continues to serve the last successful fetch so your portfolio page does not break. 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.

Poper resolves one Pixelfed account and renders supported public account media.

One of the deepest cultural differences between Pixelfed and Instagram is the absence of an algorithmic feed. Pixelfed shows photos in reverse chronological order. For embedded feeds, keep the landing-page promise to the rendered content: Poper resolves one Pixelfed account and renders supported public account media. Add page-level structured data separately when it matches your page content.

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 embed loads through the Poper snippet. Validate layout and performance on your own page after embedding.