Uploading large files Pro

Every WordPress upload normally has to fit inside one request, so the biggest file your site accepts is whatever your host allows — typically somewhere between 8 MB and 64 MB. For a policy PDF that’s fine. For a set of construction drawings, a scanned archive box or a training video it is not.

FileDeck Pro removes that ceiling by uploading large files in chunks. The file is sliced in the browser, each slice is sent as its own small request, and the server reassembles them. No single request ever approaches your host’s limit, so the practical maximum becomes your disk space rather than upload_max_filesize.

FileDeck Pro — there is nothing to configure. Large files simply upload.

What you’ll notice

Not much, which is the point. Drop a large file on Documents → Import & Export → Upload files as usual. The progress bar moves more steadily than a single-request upload, because the browser genuinely knows how much has been received rather than guessing.

The real difference shows up when something goes wrong. If your connection drops at 80%, the upload resumes from 80% rather than starting over — the server still holds the part it received and tells the browser where to continue.

The size limit

There is still a cap, deliberately. By default FileDeck accepts files up to 512 MB. The parts land on your own server’s disk while the upload is in progress, and an endpoint with no ceiling is an easy way for anyone who can add documents to fill your volume.

Site owners who need more can raise it in code:

add_filter( 'filedeck_max_upload_bytes', function () {
    return 2 * 1024 * 1024 * 1024; // 2 GB
} );

Raise it with your available disk space in mind, not just your ambitions for the library.

Who can upload

Exactly the same people as before. Chunked upload is a transport detail, not a lower bar: it requires the same capabilities as any other document upload — permission to upload files, to edit documents, and to publish them. Someone who cannot add a document normally cannot add one this way either, and an upload in progress belongs to the person who started it and nobody else.

Where in-progress files live

Parts are written into FileDeck’s protected folder, which already carries a deny-all rule, so a half-uploaded file is never reachable from the web. They are removed as soon as the upload finishes.

Abandoned uploads — a closed tab, a browser crash — are cleared by a daily cleanup after 24 hours, so an interrupted upload can still be resumed the same day but never accumulates as wasted disk space.

FAQ

Do I still need to raise my host’s PHP limits?

No. That is the point of the feature — FileDeck sizes each chunk to sit comfortably below whatever post_max_size and upload_max_filesize your server reports, so it works within your existing limits rather than fighting them.

Does this change what file types I can upload?

No. The assembled file goes through exactly the same type and extension checks WordPress applies to any upload. A file type your site does not allow is still rejected — just faster, because the name is checked before the upload starts rather than after.

Can I resume an upload tomorrow?

Within 24 hours, yes, as long as it is the same file in the same browser session. After that the parts are cleaned up and the upload starts fresh.

Does the free version have this?

The free version uploads normally, in a single request, so it is bounded by your host’s limit. Chunked and resumable uploading is a Pro feature.