How to schedule Pixelfed posts (a photo is required)

Pixelfed is a photo network on the Fediverse. Each server (pixelfed.social or a smaller instance) has its own community, rules, and timeline. You sign in on that server, upload a still, write a caption, and publish. That workflow is great for one post. It falls apart when you want a week of work queued in advance, or when the same shoot also needs a Mastodon text post and an Instagram Reel later the same day.

Native Pixelfed does not give you a cross-server content calendar. People ask for scheduling on GitHub and in forums, then fall back to personal scripts or niche Fediverse tools. A scheduler that already holds your other channels is simpler: one composer, one calendar, and Pixelfed as another destination next to Mastodon, Bluesky, or X.

The other reason is honesty about media. Pixelfed is not a text dump. A post without a photo does not belong there. Your queue should force that constraint so you never schedule a caption that will fail at publish time.

If you run accounts on more than one Pixelfed server, connect each one as its own channel. That keeps timelines separate and lets you schedule a different photo mix for each community without juggling browser profiles.

Postlaty connects to Pixelfed the same way many Fediverse tools do: you create a personal access token on your server, then paste the server URL and that token into Postlaty. The steps below match what Postlaty shows in the connect window.

1. Sign in on your Pixelfed server (for example https://pixelfed.social).
2. Open Settings → Applications and create a new token. Copy the token. Keep it private; it acts like a password for publishing.
3. In Postlaty, open Create, add a channel, and choose Pixelfed. Paste the full instance URL (including https://) and the access token.
4. Save. Pixelfed now appears in the channel picker next to your other accounts.

If connect fails, check the URL first: it must be a public https origin, with no trailing path. Then regenerate the token on the server and paste it again. To cut access later, revoke the token in Pixelfed Settings → Applications and the Postlaty connection stops working.

On Pixelfed the image carries the post. Treat the caption as support, not a blog paste. Lead with what the photo is, then add one line of context a follower would care about: where it was taken, what changed in the edit, or why you are sharing it this week.

A simple photo cadence that works for creators and small brands:

• Hero still. One strong frame with a short caption. Schedule it for the time your followers are actually awake on that server.
• Process shot. Desk, lighting, or draft. Fediverse audiences like seeing how work gets made.
• Color or detail study. A crop, a palette, or a before/after. Easy to batch-shoot and queue.
• Cross-post with care. Reuse the still on Mastodon or Bluesky if you want, but write a caption that fits each network. Mastodon takes the first image and does not take video the way Pixelfed can when the first file is a video.

Batching helps. Spend one hour shooting or generating five stills, write five captions, and schedule them across the week. That single session is usually more consistent than opening Pixelfed every day and hoping you have something to say.

If you are leaving Instagram, do not import a month of old Reels captions. Pixelfed readers expect a photo that stands alone. Shoot or generate for the Fediverse timeline, then schedule.

Scheduling is half the job. Pixelfed conversations still happen under the post. Postlaty syncs mentions and replies from your connected Pixelfed account into the Inbox, next to your other channels. You can reply from there, and the answer goes back to your Pixelfed server through the same connection.

Direct messages are not part of this path. Keep DMs on the Pixelfed web UI or app if your server offers them. For public replies, one daily Inbox pass is usually enough for a small account.