Compressing files on the server

Need to bundle a folder for download, share a multi-file package, or shrink storage? The file manager handles compression and extraction in a few clicks.

Compress files into an archive

1. Go to Services → click your hosting → Files tile.
2. Navigate to the files or folders you want to compress.
3. Select them (Ctrl/Cmd-click for multiple).
4. Right-click → Compress (or use the toolbar option).
5. Choose archive type: Zip, Tar.gz, or Tar.bz2.
6. Save. The archive appears in the same folder.

Pick the right format

• Zip — universal. Opens on every OS without extra tools. Slightly less compression than gzip.
• Tar.gz — Linux/macOS standard. Better compression than zip. Windows can open with 7-Zip or WinRAR.
• Tar.bz2 — best compression but slowest. Worth it for large archives you'll move infrequently.

For sharing with non-technical recipients, use Zip. For internal use or backups, Tar.gz is fine.

Extract an archive

1. In the file manager, navigate to the archive.
2. Right-click → Extract (or use the toolbar).
3. Pick destination folder (default is the current folder).
4. Confirm. Files extract within seconds for typical archives, longer for large ones.

The file manager handles .zip, .tar.gz, .tar.bz2, .tar, and .gz automatically.

Common uses

Bundle a project for download

Compressing a /projects/site-redesign/ folder lets you download the whole thing as one file via FTP or the file manager's download.

Migrate from another host

If you're moving in from another host:

1. They give you a .zip or .tar.gz of your old site.
2. Upload it to your hosting (FTP for big archives).
3. Extract in place. Your old site is now live (after DNS points here).

Hand a site to a developer

Compress the whole public_html/ and a .sql dump of the database; send the developer the archive. They can spin up a local copy.

Save space

If you have an archive of old stuff you might want later, leave it compressed instead of expanding it. Disk quota counts the archive size, not the uncompressed contents.

Limits

• Big files: archives over a few GB may time out in the file manager. Use SSH and tar directly if you have shell access, or chunk the data.
• Disk quota: compressing a big folder still requires temporary disk space for the archive. If you're at 95% disk usage, you may not have room.
• Open files: compressing a folder while files in it are being written (active database, busy log file) may produce inconsistent archives. Stop active processes first if integrity matters.

SSH alternative

For programmatic compression on plans with shell access:

# Compress a folder
tar -czvf myarchive.tar.gz /path/to/folder

# Extract
tar -xzvf myarchive.tar.gz

# Just zip (more universal)
zip -r myarchive.zip /path/to/folder

This is also the fastest path for huge folders — bypasses the file manager's HTTP overhead.