We build & run this

Cloudy File Manager — Safe Access in wp-admin

A file manager runs inside somebody else’s WordPress, alongside plugins we have never seen, and hands users the filesystem. It has to work everywhere and it must not become the way in.

View it live ↗
Australian-based team Senior developers only Fixed quote before we start
10k+
Files handled per install
v1.11
Shipped and maintained
WP 5.6+
Compatibility floor
Client
5eves
Industry
WordPress plugin
Scope
Plugin development & ongoing maintenance
WordPress PHP 7.4+

Australian team

Based here, working your hours — not a timezone away

144+ projects delivered

Over 10+ years building and maintaining sites for Australian businesses

One developer, start to finish

The same person every time — no re-explaining your site

Straight answers, on your terms

We only take work we can finish. Ask us anything first — no obligation

The challenge

  • It installs into WordPress sites with unknown themes and plugin stacks — conflicts cannot be debugged after the fact on someone else’s production site.
  • File management is inherently dangerous functionality: read, write, move and delete on the server.
  • Large file uploads run straight into PHP execution and memory limits that vary by host.
  • Bulk operations across thousands of files cannot block the request or exhaust memory.

What we did

  • Every destructive operation is gated behind WordPress capability checks and nonce verification, with input sanitised at the boundary.
  • Resumable uploads so large files survive a dropped connection or a host’s execution limit rather than restarting.
  • HTTP Range downloads so large files stream instead of being loaded into memory.
  • Copy, move and delete operations are queued rather than run inline, so bulk work across 10,000+ files does not time out.
  • Directory scanning to locate files across a large tree, plus zip compress and extract in place.
  • Syntax-highlighted code editing for the cases where the reason you opened a file manager was to fix one line.
  • Tested across multiple live WordPress installations to catch conflicts before release, not after.

The outcome

  • Shipped and maintained at v1.11.0, supporting WordPress 5.6+ and PHP 7.4+.
  • Handles installations with 10,000+ files without blocking or timing out.
  • Capability-gated and nonce-verified throughout.
  • Actively maintained — released, supported and updated by us.

Got something similar?

Tell us what is happening and we will come back with a fixed quote and a timeline, usually within one business day.

Get a fixed quote

Why CloudyWP

We build websites that earn their keep — fast, custom, and yours outright — then automate the work around them, so your business spends its hours on customers instead of admin.

Get a fixed quote

02 — How we work

From first call to live — four steps, no surprises.

Every CloudyWP project runs the same way, whether it is a one-page site or a store with a thousand SKUs. Here is exactly what happens.

01

We map what you actually need.

A single scoping call, then a written plan: what gets built, what it costs, and when it ships. No discovery-phase invoices, no moving targets.

Typically 48 hours

02

We design and build it properly.

Custom WordPress or Shopify on clean code you own outright. Every build ships fast, passes Core Web Vitals, and is handed over documented.

2–6 weeks typical

03

We automate the busywork.

Your site talks to the tools you already run — CRM, invoicing, email, stock. The repetitive admin stops being someone's job and starts running itself.

Average 15 hrs saved weekly

Scope A fixed quote, in writing

Deliverables, price and dates agreed before a line of code is written.

  • Free scoping call
  • Written scope document
  • Fixed price, no hourly creep

48 hrs to your quote

Get a quote