MediaHub

MediaHub for Agency Owners

Running client projects in ProcessWire is great right up until your team starts spending time on things that shouldn't take time. Uploading the same logo for the third time. Hunting down which version of a hero image is the current one. Rebuilding crop configurations on every new template. MediaHub is a one-time investment that tends to pay for itself quickly, just in hours not spent on media admin.

What it means for your projects

A shared media library means your developers set things up once and your clients — and their content teams — manage assets from a single organised place. Less time debugging missing images, less time answering "where do I upload this?", and less chance of a client accidentally deleting something that's referenced across a dozen pages.

We think you'll like…

›
One licence covers your client sites — the Scale, Studio, and Agency plans are designed for multi-site use. You're not paying per client.
›
Reduced dev time per project — the template API, crop presets, and import tools are all ready to go. You're not building media management infrastructure from scratch on each site.
›
Usage tracking protects your clients — before anything can be deleted, editors can see exactly which pages reference it. Fewer panicked calls about broken images.
›
Centralised alt text — set it once on the asset and it's consistent everywhere that asset appears. Less to brief editors on, fewer accessibility issues slipping through.
›
Collections and folders — your clients can organise their library in a way that makes sense to them, not just a flat list of files.
›
Smart import on new projects — if a client hands you a site with years of images already uploaded to page fields, the import tools can bring them into MediaHub without starting fresh.
›
Per-page caption overrides — editors can write a context-specific description for each use of an image without touching the global asset. Useful for galleries, blog posts, case studies.
›
Active development — MediaHub has shipped regular updates since launch. You're buying into something that's moving forward.
›
14-day money-back guarantee — if it doesn't fit a project, there's no risk in trying it.

Tips for agency owners

Things worth knowing once you're past the first install — easier handoffs, better client relationships, easier to justify as a line item.

Set up crop presets during project setup, not at the end

Crop presets apply site-wide and are defined in MediaHub configuration. Setting them up early — as part of your standard template and field setup — means editors can start working with cropped images from day one. Leaving it until late in a project usually means editors have already uploaded a lot of assets and have to go back and crop everything.

Labels are a simple way to add workflow without custom development

Before you hand a site over, spend ten minutes setting up a handful of labels that match how the client's team works. Something like Approved, Needs replacing, and Archive can give a content team a lightweight asset workflow without any custom module work. Show them how to filter the library by label during training and it usually sticks.

Collections can mirror a client's existing folder structure

If a client is used to organising assets in folders on a file server or Google Drive, match that structure in MediaHub's collections. It makes the transition much smoother and reduces the amount of reorganisation they feel they need to do. Set up the hierarchy before handing over so the library already makes sense when they log in for the first time.

Usage tracking is worth covering in client training

A lot of clients are nervous about deleting things in a CMS. Showing them the usage tracking on the asset detail page — where they can see every page an asset is referenced on before doing anything with it — tends to build a lot of confidence. It's a small thing to include in a handover but it reduces the "I deleted something and now a page looks broken" calls.

The software never expires — that's worth communicating to clients

If a client ever asks what happens when the licence runs out, the answer is that nothing stops working. They keep using the version they have. Updates and support stop after year one unless you renew, but the module keeps working indefinitely. That's a reassuring thing to be able to say and it's honest, which tends to matter to clients.

The Scale plan is often the right starting point for freelancers

If you're a freelancer with a small number of active client sites, Scale (three sites) is often enough and significantly cheaper than Studio. If you grow past three, upgrading is straightforward. Agency is specifically worth considering when you have multiple developers who need access, since it includes team seats.

Also written for

Developers Content Editors Marketing Teams

Launch Pricing

Choose your plan

One-time licence — the software never expires. Includes 1 year of updates and support.
After year 1, optionally enable Auto Renew for continued releases and priority help.

Final checkout price may be adjusted by our payment provider based on your location. All prices exclude applicable tax/VAT.

Solo

$79 $99

For developers using MediaHub on a single production site with all components included.

1 production site
All module components
1 year of updates
1 year of support
Optionally renew for $29/yr

Scale

$149 $199

Save on the Solo plan by licensing up to 3 client sites in a single purchase.

Up to 3 sites
All module components
1 year of updates
1 year of support
Optionally renew for $55/yr