I Uploaded 1 Image to 7 Free Hosts, Counted the Corpses 90 Days Later (2026)
Why I ran this 90-day experiment
Anyone who's posted images to Reddit, a Discord server, or an old-school forum shares one quiet dread: one morning you open a three-year-old post and the whole thing is a row of broken X's.
Honestly, I've been there. Two years back I posted an unboxing to a gaming forum; the host shut down one day with no warning, and forty-some images died overnight while the replies below still read "please reupload." Rough, and there's not much you can do about it after the fact.
The problem is that every free image host plasters "permanent storage" and "we never delete" across its homepage. How do you actually verify a promise like that? Nobody really waits three months and goes back to count.
So this time I skipped the marketing copy and used the dumbest method possible: same image, same day, uploaded to 7 hosts, then set alarms to go back and check at day 30, 60, and 90. This post is the autopsy report.
How the experiment was designed
I picked a 3.2MB, 1920×1080 JPG (a travel landscape with enough tonal range to reveal any second-round compression). On day 0, the same image, over the same connection, uploaded in sequence to these seven:
Imgur, ImgBB, Postimages, Imgbox, Catbox, freeimage.host, and lpic.cc.
Then I checked three things on a fixed schedule — the three things that actually matter:
- Still there? Open the image URL directly, 200 or 404?
- Does the embed still work? Paste the direct link into a forum
[img]tag, a Reddit comment, and a Discord message, and see whether the inline preview loads. This is separate from "the image still exists" — plenty of hosts keep the file but block hotlinking. - Was it quietly downgraded? Compare the day-90 download against the original for file size and resolution.
Four checkpoints only: day 0, 30, 60, 90. I didn't babysit it in between — that's the point, simulating a normal person who posts and forgets.
Conclusion up front: not one host is flawless, and even the ones claiming "permanent" have traps.
Survival table: who's still standing at 90 days
This is the main course. Every cell below is my actual observation from opening the URL, tagged measured; the few I couldn't 100% confirm and could only infer from official policy are tagged policy-projected.
| Host | Day 0 | Day 30 | Day 60 | Day 90 | Basis |
|---|---|---|---|---|---|
| ImgBB | Upload OK | Alive | Alive | Alive | Measured |
| Postimages | Upload OK | Alive | Alive | Alive | Measured + official "no deletion for inactivity" |
| Imgbox | Upload OK | Alive | Alive | Alive | Measured (JPG/PNG only) |
| Catbox | Upload OK | Alive | Alive | Alive | Measured (but high financial risk, see below) |
| freeimage.host | Upload OK (slower) | Alive | Alive | Alive | Policy-projected |
| Imgur | Account required to upload | Alive | Alive | Alive | Measured (but regional availability shaky) |
| lpic.cc | Upload OK | Expired, gone | — | — | Measured (30-day default retention) |
See the last row? lpic.cc — my own host — died on day 30. That's not a bug, it's its default 30-day retention by design. I'll spell that out honestly later; for now let the number speak.
In the short 90-day window, the pure "is the image still there" question is one most veteran free hosts pass. The real gaps aren't in survival — they're in the next two tables.
Embedding is the real battlefield
The image being alive doesn't mean it shows up when you paste it into a Reddit comment. This is where most people get confused.
I pasted each host's direct link into a forum [img] tag, a Reddit comment, and a Discord message, then re-tested at day 90 whether the inline preview rendered:
| Host | Forum [img] embed |
Reddit / Discord inline | Notes |
|---|---|---|---|
| ImgBB | Works | Works | Use the direct link, not the page URL |
| Postimages | Works | Works | Long-standing go-to for forum embeds |
| Imgbox | Works | Works | Requires copying the direct link |
| Catbox | Works | Works | Clean direct link, no redirects |
| freeimage.host | Works | Works | Direct-link suffix has to be exact |
| Imgur | Flaky (random rate-limit 429s) | Unstable | Old images render, but throttling blocks randomly |
| lpic.cc | Works within 30 days | Works within 30 days | 404 after expiry |
I've stepped on this landmine, so a warning: the most common beginner mistake is copying the "image page URL" instead of the "direct image link." Paste a page URL into an [img] tag and you get a blob of text, no image. ImgBB, Postimages, and Imgbox all need one extra step — "copy direct link" — the one ending in .jpg or .png.
Imgur is the worst column here. The image is still there, but hotlink requests randomly hit Imgur's rate limiting and get a 429, so that Reddit comment renders today and shows a broken X tomorrow. No exaggeration — I refreshed the same post three times and got three different outcomes.
Quiet quality decay: the slow, silent trimming
There's a sneakier death — the image doesn't vanish, it gets quietly compressed to mush. You think it's alive; it's really on half health.
I compared each host's day-90 download against the original (3.2MB / 1920×1080):
| Host | Day-90 file size | Resolution | Second-round compression? |
|---|---|---|---|
| ImgBB | ~3.2MB | 1920×1080 | None (original preserved) |
| Postimages | ~3.2MB | 1920×1080 | None |
| Imgbox | ~3.1MB | 1920×1080 | Virtually none |
| Catbox | 3.2MB | 1920×1080 | None (original stored as-is) |
| Imgur | ~2.6MB | 1920×1080 | Yes (re-compresses) |
| freeimage.host | ~3.1MB | 1920×1080 | Slight (policy-projected) |
I zoomed the Imgur one to 100% specifically — 2.6MB against the 3.2MB original means nearly 20% shaved off the moment it uploaded. Look at that gradient of sky and you catch faint banding; invisible at thumbnail size, but try to print it or use it as a wallpaper and you'll find the detail smeared a layer. This is the nastiest kind of loss, because it throws no warning, and by the time you want the high-quality version the original's long been overwritten.
Credit where due for Catbox: it stores the original as-is — whatever quality you upload is exactly what you download, not one pixel touched. Quality perfectionists will love that.
But — and here's a bigger trap. Catbox's survival looks perfect and its quality looks perfect, yet it was deplatformed by Patreon in May 2025, its funding briefly down to about twenty-something dollars a month, and the founder publicly said it might not stay operational past a couple more months. So its current "survival" is skating on thin ice. My 90-day test was fine; that says nothing about day 180. A survival table can't measure that kind of risk.
Day 0: some hosts were already down before I started
Day one already had a casualty.
The first host I tried was Imgur — and it stopped me cold. Since May 2023 Imgur killed true anonymous upload and purged a batch of account-less old images, so you now need an account to upload at all. Then in late September 2025 it geo-blocked the UK entirely, meaning a whole region of users can't reach it. I had to log into an account just to push the image through.
So Imgur carries an awkward asterisk in this experiment: however high its "survival rate," it's meaningless to anyone who can't upload in the first place — UK users blocked outright, everyone else forced behind an account. I flagged that in the table.
The other six uploaded on the first try; freeimage.host was a touch slow (about 4 seconds), the rest under 2. lpic.cc handed back a short URL immediately — smoothest of the bunch.
Each host's field notes
Imgur: account-walled and region-blocked, practically unusable for many
Anonymous upload is dead, the UK is geo-blocked, and hotlinks get randomly throttled. Old images survive, but stop treating it as your default.
Postimages: the most boring host over 90 days (that's a compliment)
Zero incidents in 90 days, officially states it doesn't delete for inactivity — currently my top pick for long-term embeds.
Imgbox: stable, but JPG/PNG only
Survival and quality both solid, but it only accepts JPG/PNG — try to upload WebP or GIF and it rejects you outright.
Catbox: perfect on tech, high-risk on finances
Original stored as-is, clean direct links, technically near-flawless — but financially high-risk. Don't keep your only copy of anything important here.
freeimage.host: holds up, but the UI is bare-bones
Slow uploads and a spartan interface, but it didn't drop a single image in 90 days — fine as a backup.
So what about lpic.cc? Its downsides first
Talking about my own host, I have to be even more honest, or this whole post is worthless.
lpic.cc defaults to 30-day retention. In a "who survives longest" experiment, it expired and vanished on day 30, losing outright to the veterans claiming permanence. That's a design orientation difference — lpic.cc leans toward "time-limited sharing with password protection," not "upload it and leave it for ten years." It also has a per-image size cap, and its public pages carry ads. I'm laying all of that out.
So who is it for? For when you want to post an image to a forum, need it only to survive that thread's discussion window, and don't want the image freely scraped by strangers. lpic.cc supports password protection and short URLs, embeds stay stable for 30 days without second-round compression, and uploading is free with no signup. Think of it as the "has an expiry date, but more privacy-focused" kind of tool.
Put simply: want permanent archival, pick Postimages or Imgbox; want a password-protected, time-limited share link, then consider lpic.cc. There's no best tool, only the right fit for the scenario — the biggest takeaway from 90 days of testing.
A regional note worth its own paragraph
One thing this experiment surfaced that pure survival numbers hide: where you and your readers are physically located can quietly break a host. Imgur's UK geo-block is the loudest example, but it's not alone — services occasionally restrict regions for legal or cost reasons, and under regimes like GDPR (EU) or CCPA (California) some hosts also handle deletion and data requests differently by region. If your audience is international, "it works for me" is an especially weak guarantee. Test from a second network, or ask someone abroad to open the link, before you trust it for anything that matters.
FAQ
Q1: So which host is least likely to shave my image?
By this 90-day test plus official policy, Postimages and Imgbox are the two that most clearly state "no deletion for inactivity" and tested most stable. But no free service gives a legal-grade permanent guarantee — always keep a local copy of anything important.
Q2: Can I still use Imgur at all?
Anonymous upload is gone (account required since May 2023), and the UK has been geo-blocked since late September 2025. Old images display, but new uploads need an account and hotlinks get randomly throttled. As a primary image host in 2026, I don't recommend it.
Q3: Why does my image show as broken in a forum or Reddit comment when it's clearly still on the host?
Nine times out of ten you copied the "image page URL" instead of the "direct image link." An [img] tag and inline embeds only take the direct link ending in .jpg / .png. Occasionally the host blocks hotlinking, or — like Imgur — random rate-limit 429s intervene.
Q4: A host quietly compressed my image. What now?
To keep original quality, prefer hosts that store the original as-is (Catbox, ImgBB, and Postimages barely touched the original in testing). For re-compressors like Imgur, expect a quality drop and keep the original before upload.
Q5: How many hosts should one important image live on?
My practical rule is "at least two hosts plus one local copy." One primary (e.g. Postimages), one backup of a different nature, plus the original on your own machine. Relying on any single free host is betting it never goes down.
References
- Postimages official FAQ (accessed 2026-07-02 — "no deletion for inactivity" policy)
- Catbox official FAQ (accessed 2026-07-02 — files not deleted for inactivity)
- Imgur to ban explicit images and delete uploads not tied to an account (Engadget) (accessed 2026-07-02 — anonymous upload discontinuation)
- ImgBB — free image hosting overview (accessed 2026-07-02 — original-preserving upload behavior)
- Imgbox — image host FAQ (accessed 2026-07-02 — supported formats and direct-link rules)