Heads-up
Native image attachments stay the most engaging way to post in the fediverse — but a permanent external URL is invaluable when toots get boosted across instances and you want a stable canonical source.
Step by step
1. Upload to swiftimg
Drop the file at /upload (anonymous works) and copy the viewer URL.
2. Toot with the URL
Most Mastodon clients render an OG card for any URL on the first line of a post. Paste the swiftimg viewer URL.
Toot Look at this: https://swiftimg.com/i/abc1233. Or attach natively + link for context
Attach the image to the toot for the in-feed render, and link the swiftimg URL in the body for boosts that traverse instances with patchy media caching.
Mastodon — FAQ
Will the link survive an instance move?
Yes. Mastodon-native uploads live on the original instance; if that instance goes down or you migrate, the media URL can break. swiftimg URLs don't.
Do all fediverse clients show OG cards?
Most do — Mastodon, Pleroma, Akkoma, and Misskey. Some lighter clients show only the bare URL. Native attachments cover the gap.
What about Mastodon's content-warning / CW workflow?
CW is a Mastodon UI thing; it doesn't affect how external URLs render. Use the CW field for sensitive content even when linking out.
See also
Image hosting for Twitter / X
Host images on swiftimg and link them from a tweet or X post. The link previews inline via Twitter Card metadata, with no upload limit and a permanent URL.
Image hosting for Bluesky
Upload to swiftimg and link from a Bluesky post for an inline preview. Useful when you want a permanent URL or need to share more than four images.
Image hosting for LinkedIn
Host images on swiftimg and embed them in LinkedIn articles via Markdown or as a link with an OG card. Permanent URL, globally cached, no expiry.
swiftimg vs ImgBB
An ImgBB alternative with faster delivery, automatic WebP, and a real developer API.
Ready to host your Mastodon images?
Start free, then unlock the full API, transforms, signed URLs, and a custom domain on the Developer plan.