Panel & filesA zip that extracts instantly on your own computer can hang and fail in the browser file manager — not because the file is too big for the server, but because the web request unpacking it is only allowed to run for so long before the web server itself cuts it off.
Why the browser path has a ceiling and SFTP does not
Extracting through the web file manager happens inside a single HTTP request: your browser asks the web server to unpack the archive, and the web server's own script execution timeout limits how long any one request may run before it is killed, regardless of whether the extraction itself was still progressing normally. A large archive can simply need more time than that ceiling allows. An SFTP client, by contrast, is not bound by any web request lifecycle at all — it streams files directly over its own connection with no comparable timeout, which is why the same archive that fails in the browser extracts without issue once it is unpacked locally and the files are uploaded directly.
For anything sizeable
- Extract the archive on your own computer first
No timeout applies locally, and it is almost always faster than uploading a compressed file and waiting on the server to do the same work.
- Upload the extracted folder via SFTP
A direct file transfer has no equivalent script-execution limit to hit.
- Reserve the browser extractor for genuinely small archives
It remains the faster, more convenient option for anything comfortably under the timeout — the SFTP route is only needed once size becomes the constraint.
About this guide: An original guide from the EnduranceNodes team, written for the servers we host. If a step no longer matches what you see, tell us and we will update it.