Add a Real Image Upload Button to Your phpBB, SMF, or MyBB Forum

Anyone who has moderated a forum for more than a few months has run into the same problem: members hotlink images from wherever is convenient, those links break the moment the original host deletes the file or changes its structure, and years of old threads slowly fill up with broken image icons. The fix most forums land on eventually is running their own image hosting, which trades one problem for another: server costs, storage limits, and one more thing to keep patched and backed up. YourImageShare's forum plugins offer a middle path, a real upload button inside the post editor that uploads to YourImageShare instead of the forum's own server, with none of the hosting overhead.

How it works, in one sentence

Each plugin adds an Upload Image button next to the post editor's text box. Click it, pick a file, and a direct link is inserted as BBCode at your cursor automatically, using the same upload API documented at yourimageshare.com/about/api. No separate tab, no manual copy and paste of a URL from somewhere else.

phpBB

phpBB is one of the most widely deployed forum platforms still in active use, and it has a proper extension system for exactly this kind of addition. The plugin ships as a real phpBB 3.2 and 3.3 extension: unzip it into your installation's ext directory, enable it from Customise, Manage extensions in the admin control panel, then paste your real API key into the extension's template file in place of the placeholder. From that point on, the upload button appears automatically on every page with a post editor, no further configuration needed.

SMF (Simple Machines Forum)

SMF has its own package manager built specifically for installing mods like this one. The plugin is a real SMF package, installed the normal way through Admin, Package Manager, after which the only remaining step is replacing the placeholder API key in a single source file with your real one. SMF's package system handles registering the integration cleanly, without needing to touch any of the forum's own theme files directly.

MyBB

MyBB plugins live in a straightforward inc/plugins directory, and this one is a real MyBB 1.8 plugin using MyBB's own documented hook system. Copy the plugin file into place, activate it from Configuration, Plugins in the admin panel, and set your API key in the same file. As with the other two, the button then appears automatically everywhere a post editor does.

FluxBB, PunBB, and ZetaBoards

These three do not have a formal plugin or extension system the way phpBB, SMF, and MyBB do, so integrating them is a small copy and paste snippet instead of an installable package. For FluxBB and PunBB, a short script tag goes directly into your active style's template file. For ZetaBoards, which is a hosted platform rather than something you install yourself, the same snippet goes into the Board Template section of the Admin CP, a feature built for exactly this kind of sitewide customization without needing file access. Full copy and paste instructions for all three are linked from the API documentation page.

Why this beats self-hosting images for a forum

Running your own image hosting for a forum means paying for storage that only grows over time, since almost nobody goes back and deletes old attachments, and it means one more system that needs backups, security patches, and monitoring. Pointing uploads at YourImageShare instead moves that entire cost and maintenance burden off your own server. Members still get a real, permanent, working image link inserted directly into their post, it just is not stored on infrastructure you have to maintain yourself.

Why this beats relying on random third-party image hosts

The alternative most communities actually end up with, without any plugin at all, is members individually choosing whatever image host they personally use and pasting a raw link into their post. This is exactly what causes the broken-link problem in the first place: every member picks a different host, some of those hosts eventually shut down or start deleting old free-tier content, and old threads slowly rot. A forum plugin standardizes on one host for everyone, with a consistent, direct link format, uploaded the same way every time, right from the post editor instead of a separate tab that is easy to skip.

Setting expiry on forum uploads

Not every forum upload needs to be permanent. A one-time attachment for a support thread, a temporary screenshot proving a bug exists before it gets fixed, or a promotional image for an event that already happened, none of these need to live forever cluttering storage. The same expiring uploads feature available through the wider API applies here too, letting a file quietly disappear after a set time rather than sitting around indefinitely. Full details on how the timing works are documented on the API reference page.

One API key, every member

A detail worth planning for: the plugin uses a single API key configured by whoever installs it, typically the forum's admin, not a separate key per member. That means every upload made through the plugin counts against one account's rate limits and usage, which is generally fine for small to medium communities but worth checking against the documented limits if the forum is very high traffic. Rate limits and how to read the response headers that report them are covered in full on the API documentation page.

Getting started

Every plugin, along with exact installation steps for each platform, is linked from yourimageshare.com/about/api under Forum Plugins. You will need an API key first, generated in under a minute from My account after signing in at yourimageshare.com, and the free tier's rate limits are generous enough for most community forums without any need to upgrade.

Testing before rolling it out to your community

Before announcing a new upload button to an entire forum, it is worth testing the installed plugin yourself first, ideally in a private or staff-only test board if your forum has one. Post a test message, click the upload button, confirm the resulting link actually resolves and displays correctly, then delete the test post. This catches the two most common setup mistakes early: an incorrectly pasted API key, which usually shows an authentication error the first time someone tries to upload, and a plugin that was copied to the wrong directory, which usually means the button never appears at all. Both are quick to fix once caught in testing, and much less visible than discovering them from a confused member posting in the help forum after launch.

A note on moderation

Every file uploaded through YourImageShare, whether through the website, the API directly, or one of these plugins, goes through the same automated moderation check applied to any other upload on the platform. This does not replace whatever moderation policy your own forum already runs, member behavior and post content are still your community's responsibility, but it does mean the underlying image hosting itself is not a completely unmoderated dumping ground, which matters if you are choosing between this and a truly anonymous, unmoderated third-party host for your members to use instead.

Rolling this out alongside existing image hosting habits

Most forums that have been running for a while already have members with existing habits, some hotlinking from personal hosting, some from whatever free image host they have always used. A plugin does not force anyone to change that behavior, it simply adds a faster, more reliable option sitting right next to the text box. In practice, once members try the one-click upload button a few times and notice the resulting link never breaks the way an old hotlinked image eventually does, adoption tends to happen on its own without needing a forced migration or a rule change. Pinning a short announcement thread explaining the new button, linking to the API documentation page for anyone curious how it works, is usually enough.

If your forum software is not listed

phpBB, SMF, MyBB, FluxBB, PunBB, and ZetaBoards cover a large share of forums still actively running today, but they are not the only options out there. Any forum software that can render a small HTML and JavaScript snippet in its page template, which covers the overwhelming majority of self-hosted forum platforms, can use the same underlying widget the FluxBB and PunBB integrations use, a page-editor button that uploads through the API and inserts BBCode automatically. Full technical details on the endpoint it calls are documented at yourimageshare.com/about/api for anyone comfortable adapting the snippet to a different platform.

What members actually see

From a member's point of view, nothing about posting changes except one new button. They do not need an account on yourimageshare.com, do not need to know the upload is even happening through a separate service, and do not need any instructions beyond "click this button to add an image." The link it produces behaves exactly like any other image link pasted into a post, previewing normally and working the same way years later, which is the entire property that makes this worth setting up in the first place.

Encouraging adoption without forcing it

A short pinned post explaining the new button, with a link to YourImageShare for anyone curious what is actually hosting the images now, tends to be all that is needed. Forcing a migration away from old habits rarely goes well on an established community, while a genuinely faster option sitting right next to the text box tends to win people over on its own within a few weeks.

The setup itself takes a few minutes per platform, and once it is done it stays done, with no ongoing maintenance beyond the same admin panel updates a forum already needs from time to time.

A quick comparison worth having ready

If members ask why the forum moved away from letting everyone hotlink from wherever they liked, the short version is reliability. A link generated through YourImageShare stays working because the platform exists specifically to host that file long-term, the same way yourimageshare.com works for anyone uploading directly through the website. A link to wherever a member happened to have an account five years ago has no such guarantee, and a meaningful share of old, broken images across the web trace back to exactly that pattern.

If the forum's members would also benefit from uploading straight from a screenshot tool rather than a saved file, a companion post on this companion post covers setting up ShareX, Flameshot, and Greenshot integrations, which pair naturally with a forum plugin for anyone documenting bugs, sharing screenshots, or answering support questions with visual proof.

None of this requires touching the forum core software itself, which matters for anyone wary of anything that complicates future upgrades down the line.

If BBCode formatting itself (not the upload step) is the part you need a reference for, see BBCodes, HTML tags, and embeddable frames. For a script-based bulk upload instead of a plugin, see automating uploads with the API.