Direct Image Links for Forums, Blogs, and Discord

"Just share the link" sounds simple until you paste it somewhere and get a broken thumbnail, a redirect, or nothing at all. The problem is almost always the same: you shared the wrong kind of link. There are three, and platforms care deeply about the difference.

The three kinds of image links

The page link — a URL to a web page that shows the image. Example:https://example.com/i/AbC123. Great for humans, useless inside an<img> tag.
The direct link — a URL that returns the image file itself. Example:https://example.com/img/AbC123.jpg. This is what you paste into chat apps, forums, and embed markup.
The embed snippet — platform-specific markup that wraps the direct link: HTML, BBCode, or Markdown.

A quick sanity check: open the link in a new tab. If you see the image alone on a blank page, it's direct. If you see a website around it, it's a page link.

Which format to use, by platform

Traditional forums

Most forum software (phpBB, vBulletin, XenForo, SMF) renders[img]https://…[/img]. Paste the BBCode snippet and the image appears inline. If a forum only supports HTML, use the <img> tag instead.

Reddit, GitHub, and Markdown tools

Use ![alt text](https://…). The alt text isn't decoration — it's what people see if the image fails to load, and what screen readers announce. Write something meaningful.

Discord, Slack, and chat apps

These unfurl direct links automatically, so paste the bare URL with no markup. If the embed doesn't appear, check that the link ends at the image file and doesn't redirect through a landing page.

Your own website or blog

Use HTML. Add alt, width, and height attributes where you can — explicit dimensions stop the page from jumping as images load, which is one of the most common causes of a poor layout score.

Why some image links break

If an image worked yesterday and is broken today, one of these is usually responsible:

Hotlink protection. Some hosts only serve images when the request comes from their own site, so the link works on the host and nowhere else.
Expiring or signed URLs. Cloud storage links often include a signature and an expiry time. They're fine for an hour and dead after that.
Page links used as image links. An tag pointed at an HTML page renders nothing.
The file was deleted. If the owner removed it, every link to it stops working.

The fix for the first three is to use a host that gives you stable, unsigned, direct URLs. That's the whole point of an image host — the link you get today should still work next year.

How imgbb generates your links

Every upload — anonymous or not — gets a permanent page at /i/<id> and a direct file URL under /img/<id>.jpg. The uploader copies all four formats to your clipboard with one click:

Direct link for chat and email
HTML for websites and blogs
BBCode for forums
Markdown for GitHub, Reddit, and docs

You can revisit any image's page later to copy the snippets again — useful when you only saved the image page URL, not the code.

A note on hotlinking ethics

Hotlinking — embedding an image hosted elsewhere — is what image hosts are for, but it's worth being considerate. Don't hotlink huge files, don't strip attribution from work that isn't yours, and don't use someone else's bandwidth to serve your production traffic volume. For a forum post or a personal blog, it's completely fine.

Frequently asked questions

Why does my image show as a clickable link instead of rendering?

You used the page link instead of the direct link. Grab the direct URL from the image page and try again.

Do direct links expire?

No. imgbb links stay valid until the image is deleted or removed for violating the terms.

Can I use the same image on multiple sites?

Yes — the same direct link works everywhere. There's no per-site limit and no referrer restriction.

TL;DR

Page link for humans, direct link for chat, HTML for websites, BBCode for forums, Markdown for GitHub and Reddit. If an embed fails, the link type is almost always the reason.