phpBB Image Mod: How to Add Image Uploading and Fix Broken Images in Posts
A phpBB image mod (or, on modern phpBB 3.2+/3.3, an image upload extension) adds the ability to upload image files directly into a forum post instead of linking to an outside host. You need it when you want members to attach pictures from their own device, and you need the troubleshooting steps below when uploads succeed but images don't render in the post. If your forum is on phpBB 3.3, prefer an extension over a legacy MOD; if you're on 3.0.x, only the older MOD/attachment system applies.
What a phpBB image mod actually does
There are two different things people mean by "phpBB image mod," and mixing them up causes most confusion:
- Native attachments. phpBB ships with an attachment system. You enable it in the ACP, set file types and size limits, and members get an "Add files" button under the post editor. No external service is involved; files live on your server.
- An upload/embed extension or MOD. This adds or restyles the upload UI, adds drag-and-drop, or inserts the image inline with a BBCode tag like
[img]pointing at the uploaded file.
What it is not: a mod does not host your images for you. If you'd rather not store files on your own server, the alternative is an external image host — you upload there, copy the direct image URL, and paste it into the post wrapped in [img] tags. That approach needs no modification to phpBB at all.
Enabling native image uploads in phpBB
The exact menu labels vary by version, so treat these as the settings to find rather than a fixed click path.
- Turn attachments on. In the ACP, under the attachment settings, enable attachments and set a maximum file size. If this is off, no upload button appears for anyone.
- Allow image file types. Add the extensions you want (for example
jpg,jpeg,png,gif,webp) to the allowed list, and set a maximum file size per type. A type that isn't listed is rejected at upload. - Set image dimensions. Configure maximum width/height. phpBB can create a thumbnail when the image exceeds your limit, so the post stays readable.
- Check permissions. Attachment permissions are per-forum and per-group. A member can have upload rights in one forum and not another. If the button is missing for a group, this is usually why.
- Confirm the storage path is writable. The attachment upload directory must be writable by the web server. If it isn't, uploads fail silently or with a generic error.
Expected result: a member opens the post editor, sees the attachment control, uploads a file, and after submitting sees either the image or a thumbnail link in the post.
Why images don't display after upload
Work through these in order — each one produces a different symptom.
| Symptom | Likely cause | Fix |
|---|---|---|
| Upload button missing entirely | Attachments disabled, or group lacks permission | Enable attachments; grant the group upload permission for that forum |
| Upload rejected instantly | File type not in allowed list, or over the size cap | Add the extension; raise the max size |
| Post shows a link, not the image | Inline display not enabled, or the image is only attached | Use the inline placement option, or wrap the direct URL in [img] |
| Broken image icon in the post | Wrong URL, or the host blocks hotlinking | Re-copy the direct image URL; check the host's hotlink policy |
| Thumbnails fail to generate | GD or Imagick missing/disabled in PHP | Enable one of them in PHP and restart the web server |
| Images vanish after a while | External host deleted them or applied a retention limit | Self-host the files, or pick a host that keeps them |
Two of these deserve emphasis. Hotlink protection is common on free image hosts: the direct URL works when you open it in a browser tab but returns a placeholder when embedded on your forum, because the host checks the referring page. Missing GD/Imagick doesn't stop the upload — it stops phpBB from resizing or thumbnailing, so large images either fail to process or display at full size.
Self-hosted uploads vs. a free image host
Both work in forum posts; they fail in different ways.
- Self-hosted (native attachments): you control retention and there's no third-party dependency, but you pay in disk space, bandwidth, and backup responsibility. Good when images are core to the forum's content.
- External image host: zero server load and no storage cost, but you inherit the host's uptime, hotlink policy, and retention rules. Good for casual sharing and for forums where members already post screenshots.
Image Chest (imgchest.com) is one example of a free image hosting and sharing service positioned for forum image hosting, with the stated aim of keeping media uncompressed and uncensored. If you go the external-host route, the workflow is the same regardless of provider: upload the file, copy the direct image URL (not the gallery or page URL), and paste it between [img] and [/img]. The most common mistake is copying the page URL instead of the file URL — that produces a broken image every time.
Choosing between the two
Pick native attachments if you want images to persist as long as the forum does and you can manage storage. Pick an external host if you want no server maintenance and your members mostly share one-off screenshots. You can also run both: native attachments for permanent content, external links for quick shares. Whichever you choose, verify the result by viewing the post as a logged-out guest — permission and hotlink problems often only show up for users who aren't you.