Desktop Pricing Docs Blog About GitHub View as Markdown (Agent) Get started
Human Agent
← Back to blog

imgbox is down? Here's how to rescue your images before they're gone.

imgbox has been throwing 503s and connection timeouts, and people are openly asking whether it's dying. If your posts and forum threads embed imgbox images, there's a window to save them right now — and an honest limit on what's recoverable once a host goes fully dark. Here's both.

What's happening to imgbox

imgbox — a long-running free image host — has started returning 503 Service Unavailable and, more recently, outright connection timeouts (ERR_CONNECTION_TIMED_OUT). Outage trackers flag it as down, and threads like "Is imgbox dying or dead?" are climbing on communities like r/imguralternatives. Nobody outside imgbox knows if it's a bad week or the end — but either way, the images you hotlinked from it are now blinking in and out.

If that sounds familiar, it should. It's the same story as Photobucket's 2017 hotlink ransom, TinyPic shutting down in 2019, and Imgur's UK block and deletions. Free image hosts don't send a shutdown notice. They just start failing, and one day the failures don't stop.

The honest truth about rescuing a dying host

Let's be straight, because most "rescue" pitches aren't: if a host is fully and permanently dead, an image you never saved anywhere else is gone. Any tool that "rescues" a hotlinked image works by re-fetching it from the source — and if the source never answers again, there's nothing to fetch. Anyone promising to resurrect images from a host that's already dark is selling you something.

The good news: imgbox isn't dead — it's flapping. It times out, then briefly responds, then times out again. That flapping is a window, and it's open right now. Rescue works in these situations, most-reliable first:

  • Grab them while imgbox still has a pulse. Every time imgbox responds — even for a second — a rescue proxy can fetch the image once and serve its own durable copy, so it keeps loading even after imgbox stops. (That cached copy lasts around 30 days — enough breathing room to migrate it into storage you own and make it truly permanent.) So try repeatedly during the flapping, not once.
  • Copies you already cached survive the outage. If an imgbox image was recently loaded through a rescue proxy or CDN, that copy keeps serving even while imgbox itself is down.
  • Third-party caches, for images you never touched. The Wayback Machine, Google Images cache, and even your own browser cache sometimes still hold a copy. Best-effort, not guaranteed.
  • Your local originals. The only 100% reliable recovery for a truly dead host is re-uploading the files you still have on your computer.

So the real advice isn't "wait and see." It's act while there's still a window — every hour imgbox stays flaky is an hour you can still save what you embedded.

How to rescue your imgbox images

Fastest, no signup — the rescue tool. Paste your imgbox links into the free imgbox rescue tool. It routes each image through PixelVault's edge — so any image imgbox still answers for (or that's already cached) comes back immediately, on a URL that isn't affected by imgbox's outage. For anything imgbox won't return, it points you at a Wayback lookup so you can recover what's archived.

WordPress — one plugin, whole site. If your imgbox images are embedded across WordPress posts, install the free PixelVault Image Rescue plugin. It finds every imgbox image on your site and rewrites them to load through PixelVault's edge automatically (Live rescue), retrying through imgbox's flapping until each one is safely cached. When you're ready, add a free API key and Migrate & Own copies them into permanent URLs in a project you control — so they survive even after imgbox is gone for good. It's fully reversible; your posts are only touched when you migrate, and a revision is saved for each.

Anywhere else. Wrap each imgbox URL through the rescue endpoint — https://img.pixelvault.dev/rescue?u=<your-imgbox-url> — and the image loads from PixelVault's CDN instead of imgbox. See the rescue overview for the full picture.

Why this keeps happening — and how to stop caring

Photobucket. TinyPic. Imgur. Now imgbox. The specific host changes; the pattern doesn't. When you hotlink an image, you don't own it — it lives on someone else's server, under someone else's rules, and your page is one outage away from a blank box. The fix isn't finding a "better" free host to hotlink from next. It's owning your images: copy them somewhere you control, on URLs that don't disappear when a company has a bad quarter.

That's the whole point of Migrate & Own. Rescue buys you time today; owning them means you never have to read a "is [host] down?" thread with your stomach in a knot again.

Rescue your imgbox images now

The window is open while imgbox is still flapping. Try the imgbox rescue tool, or install the WordPress plugin to fix and migrate a whole site. Dealing with broken Imgur images too? The same plugin covers those — see Imgur images not loading in WordPress.