Every forum veteran and blog author hits the same wall eventually: you have an image, and the place you want to put it does not store images. Forums limit attachments, README files are plain text, and half the internet's old image links have already died. You need an image host, and preferably a free one.

Here is how to pick one that will not let you down, and how to use it well.

What an image host needs to do

The job sounds trivial, upload a picture, get a URL, but the differences matter:

Direct links that embed cleanly

You want a URL that ends in a real image extension or serves an image content type, so forum software, Markdown renderers, and HTML img tags display it inline. Some hosts wrap images in landing pages, which breaks embedding everywhere.

Long retention

The single biggest failure mode of image hosting is link rot. Countless forum threads from the 2010s are walls of dead boxes because a host shut down or purged old files. Prefer hosts with a track record or a clear retention policy over shiny newcomers.

Sensible limits

Check maximum file size, format support, and bandwidth caps. For screenshots and photos, a 10 to 20 MB ceiling is plenty. For big PNGs of charts and game screenshots, make sure PNG is supported properly rather than silently converted to JPEG.

The main free options

General image sharing platforms

Sites built around image sharing, like s.pub, which handles both images and short video with a focus on quick, link-first sharing. You upload, get a page and a direct link, done. Good fits: images you want to actually show people, quick embeds, and anything where a clean presentation page helps.

Classic image hosts

Imgur has been the forum default for a decade, though its policies and hotlinking rules have tightened over the years. PostImages and ImgBB remain popular free picks with simple direct links. These hosts optimize for volume and simplicity.

Developer-oriented hosts

GitHub works surprisingly well for images tied to a repository: put the file in the repo or an issue, reference the raw URL. It is free, reliable while the repo exists, and versioned. Not for hotlinking into high-traffic pages, but excellent for READMEs and documentation.

Your own storage

A cheap object storage bucket with a CDN in front is the professional answer once volume grows. pennies per gigabyte, full control, no third-party policy risk. The setup cost is real, so most casual users should stay with a host until they actually feel the limits.

How to embed once you have a link

In forums

Use the image button or BBCode:

[img]https://example.com/photo.jpg[/img]

In Markdown


In HTML

<img src="https://example.com/photo.jpg" alt="description" width="800" loading="lazy">

The loading attribute matters on content-heavy pages: lazy loading keeps a page full of images from downloading everything at once.

Habits that prevent dead links

Keep your originals

Treat every image host as a delivery layer, not an archive. Keep the source files on your own disk with real filenames.

Prefer standard formats

JPEG for photos, PNG for screenshots and sharp text, WebP when you control both ends for smaller files. Hosts that silently re-encode can blur pixel-perfect screenshots.

Descriptive filenames help you later

photo-final-v2.png tells you nothing in six months. Clean filenames also produce cleaner URLs, which read better in documentation.

Re-check old embeds occasionally

If you maintain documentation or long forum threads, a yearly check for dead images is cheap insurance. Tools exist that crawl a page and list broken image links.

Bottom line

For quick embeds and sharing, use a link-first platform like s.pub or a classic free host, and mind the retention policy more than the feature list. For documentation, consider repository-based hosting where the images live next to the text. And whatever you choose, keep originals on your own storage, because on the internet, the only image host guaranteed to still exist in ten years is your own backup.