With the cPanel File Manager can you compress files and entire folders directly on the server into a ZIP archive or extract existing ZIP files. This is practical, for example, if you want to download, upload, or move multiple website files together within your hosting account.
In this guide, we will show you step by step how to create, download, upload, and extract a ZIP archive in CURIAWEB. You will also learn what to pay attention to regarding the destination directory and overwriting existing files.
Important: Always check the destination folder and the contents of the archive before extracting. A ZIP archive can overwrite existing files with identical names or create an unexpected directory structure.
When is a ZIP archive useful in the file manager? #
A ZIP archive combines multiple files and folders into a single file. Depending on the content, the data can also be compressed in the process.
This is especially practical if, for example, you want to download an entire folder.
Instead of transferring hundreds of individual files one after another, you first create:
website-files.zip
and then download only this archive.
Conversely, you can upload a prepared ZIP archive to the server and extract it directly there.
1. Open cPanel File Manager #
Log in to your CURIAWEB cPanel and open:
Files → File Manager
If you are not yet familiar with the file manager, you can find the basics under Use cPanel File Manager.
2. Select files or folders for the ZIP archive #
Navigate to the directory where the desired data is located.
Select the files or folders you want to combine into an archive.
Check the selection carefully before proceeding.
Practical Tip: If you want to compress a complete website folder, check its size beforehand. For very large data sets, the newly created ZIP archive will also require additional storage space on your hosting account.
3. Select compress #
After you have selected the desired files or folders, select the function in the file manager Compress.
cPanel will then show you the available archive types or compression options.
For normal and widespread data exchange, choose the ZIP archive.
4. Set names for the ZIP archive #
Assign a unique name to the new archive.
For example:
website-files.zip
or:
bilder-archiv.zip
Use a name that will allow you to tell later what the archive contains.
For temporary backups, a date can also be helpful, for example:
website-before-modification-2026-08-28.zip
5. Create ZIP archive #
Then start the compression.
cPanel creates the archive in the specified directory.
With many or large files, this process may take some time. Please wait until processing is complete.
Check afterwards whether the ZIP file is present in the file manager.
ZIP file requires additional storage space #
When compressing, the original files usually remain. In addition, the new archive is created.
For example, if your website takes up several gigabytes, the ZIP archive can therefore also require considerable additional storage space.
Important: If your hosting storage is already almost completely full, creating a large archive can fail or further deplete the available storage.
6. Download ZIP archive #
If you want to save the archive on your computer, select the created ZIP file and choose Download.
Wait until the download is completely finished.
Then check on your computer if the file exists and can be opened.
Practical Tip: Do not delete the server-side archive immediately after the download starts. First, check whether the downloaded ZIP file is complete and can be opened.
7. Remove temporary ZIP archive from server #
If you created the archive only for download and no longer need it on the server, you can delete it afterwards.
This frees up the additionally occupied storage space.
Make sure to check carefully that you only delete the archive and not the original website files.
Do not leave ZIP archives lying around unnecessarily in public_html #
An archive of website files should not be stored permanently unprotected in the publicly accessible document root.
Particularly complete website archives can contain sensitive files.
For example:
website-backup.zip
within
public_html
can be potentially accessible directly via the web, depending on the server configuration and the file name.
Safety: Remove temporary website archives from publicly accessible directories as soon as you no longer need them.
Upload ZIP file to the server #
You can also use the process in reverse.
If there are many website files on your computer, it can be faster and clearer to first combine them locally into a ZIP archive.
You then upload this archive as a single file to the server and extract it there.
8. Open correct target directory #
Before you upload a ZIP archive, open the desired destination area in the file manager.
For example, if the archive contains files for the main website, depending on the domain configuration, this could:
public_html
to be.
However, a different document root can be used for additional domains.
Attention: Check the document root before uploading or extracting a website archive. A correct archive in the wrong directory will still result in an incorrect website structure.
9. Upload ZIP file #
Select in the correct directory Upload and transfer the ZIP file from your computer.
Wait until the upload is completely finished.
Then return to the file manager and check whether the archive is present in the desired directory.
We cover the uploading of files in detail under Upload, download, and edit files in cPanel.
10. Know the contents of the ZIP archive before extracting #
Before extracting the archive into a production website, you should know what directory structure it contains.
An archive can, for example, directly contain the following files:
index.php
wp-admin/
wp-content/
wp-includes/However, it can also contain an additional main folder:
meine-website/
index.php
wp-admin/
wp-content/
wp-includes/This difference is important.
Common mistake: additional subfolder #
Suppose you extract a WordPress archive to:
public_html
However, the archive already contains the parent folder:
my website
Then the actual website files can subsequently be found at:
public_html/meine-website/
lie, even though they are right under:
public_html/
are needed.
The domain may then not point to the expected website.
Practical Tip: Always check whether an archive contains the actual files directly or also includes a parent folder.
11. Select and extract the ZIP file #
Highlight the ZIP file in the file manager.
Then select the function Extract or rather Unpack.
cPanel asks for the destination directory to which the files should be extracted.
12. Check destination path carefully #
Check the suggested destination path before starting the extraction.
For example, if you in:
public_html
want to unpack, make sure that another directory is not accidentally selected.
The destination path is one of the most important points when extracting.
Attention: Do not unpack an unknown archive directly via a production website. Check the content and directory structure first.
13. Consider existing files #
Special care is required if there are already files in the target directory.
If the ZIP archive contains files with identical names, existing files can be replaced or overwritten during extraction.
This affects, for example:
index.php
.htaccess
wp-config.php
or other productive website files.
Backup before extracting over an existing website #
If an archive is to be extracted into a website directory that is already in use, you should create an appropriate backup of the existing data beforehand.
This allows you to restore the previous state in case the archive contains unexpected files or overwrites existing data.
Important: „Just unpacking it over the top is not a secure update or recovery strategy for a production website.
14. Start extraction #
Once the destination directory and the contents of the archive have been checked, you can start the extraction.
Wait until cPanel has completed the process.
With large archives or a large number of contained files, processing may take some time.
15. Check unpacked files #
Then open the destination directory and check the resulting structure.
Check in particular:
- whether the expected files are present
- whether an unexpected additional subfolder has been created
- whether files are in the correct document root
- whether file names and directories are plausible
16. Test website after extracting #
If the archive contains files of an active website, access the website directly afterwards.
Do not only check the home page, but also some subpages or the function that was changed by the new files.
If an error occurs immediately after extraction, you should not modify any further files on suspicion.
First, check which files were added or replaced by the archive.
17. Remove ZIP file after successful extraction #
If the archive is no longer needed after extraction, you can delete it from the server.
This reduces memory consumption and prevents a potentially sensitive archive file from unnecessarily remaining in your web space.
Practical Tip: First unpack, check the result and test the website - then remove the ZIP archive.
A ZIP archive is not automatically a complete website backup #
When you compress a website's directory into a ZIP file, you are initially backing up only the selected files and folders.
Many websites also use a database.
In WordPress, for example, posts, pages, settings, and much more information are stored in the database.
A ZIP archive from:
public_html
does not contain this database automatically.
Important: A ZIP file containing website files is not automatically a complete backup for a database-driven website.
ZIP archive is still suitable as a quick file backup #
Before making a targeted change to multiple files, a ZIP archive of the affected directory can be useful as an additional short-term backup.
For example, if you want to modify a specific website folder, you can compress it beforehand and download the archive.
However, you should not rely exclusively on it for a complete recovery strategy.
Cannot create archive #
If cPanel cannot create a ZIP archive, first check the available disk space.
Additional storage is required for the new archive, while the original files remain available.
Other possible causes may include very large amounts of data or technical limitations of the ongoing process.
Record a displayed error message as completely as possible.
ZIP file cannot be uploaded #
If the upload fails, check:
- the available storage space
- the size of the ZIP file
- whether the upload was completed successfully
- the target directory
- a possibly displayed error message
For very large file transfers, another transfer method may be more suitable.
ZIP file cannot be extracted #
If cPanel cannot extract an archive, the file may be incomplete or corrupted, for example.
Check on your computer, if possible, whether the archive can be opened there.
If even the local opening fails, you should recreate the archive or obtain it again from a reliable source.
Not enough memory while unpacking #
Additional storage space is also required during extraction.
If both:
website.zip
as well as the files extracted from them are on the server at the same time, both sets of data require storage space.
A nearly full hosting account can therefore reach its storage limit during extraction.
ZIP file is much smaller than the unpacked data #
This is not unusual.
Text-based files can often be compressed significantly. In contrast, already compressed formats such as JPEG images, videos, or certain other file types can be compressed much less.
Therefore, do not plan how much storage space will be needed after extraction based solely on the size of the ZIP archive.
Include hidden files in the archive #
Website directories can contain hidden files such as:
.htaccess
contain.
When creating or extracting a website archive, such files can also be relevant.
If you don't see them in the file manager afterwards, you may need to enable the display of hidden files.
We show the procedure at Show hidden files like .htaccess in cPanel.
Received a 500 error after extracting #
If the website immediately after unpacking a 500 Internal Server Error show, for example, overwritten configuration files or a non-matching .htaccess-file play a role.
First, check which files the archive has modified.
We show how to systematically investigate such an error at Fixing a 500 Internal Server Error.
Received a 403 error after extracting #
If instead a 403 Forbidden appears, access rules or file permissions, among other things, may be relevant.
Do not set the permissions globally to 777.
We explain the file permissions under How to correctly set file permissions 644 and 755 in cPanel.
Do not unzip ZIP files from unknown sources #
A ZIP archive can contain executable PHP files, scripts, or other content.
Therefore, do not unpack unknown archives into a publicly accessible website directory.
Safety: A ZIP archive is merely a container for files. It says nothing about whether the contained files are trustworthy or secure.
Do not accidentally save the complete website twice #
Manual uploads quickly create directories like:
public_html/backup/
public_html/website-alt/
public_html/wordpress-kopie/
Such copies can consume storage space and potentially remain accessible via the internet.
Therefore, after completing your work, check which temporary files and directories are actually still needed.
Recommended procedure for downloading a folder #
- Open the cPanel File Manager.
- Navigate to the desired folder.
- Mark the required data.
- Choose Compress.
- Create a ZIP archive.
- Download the archive.
- Check on your computer if it can be opened.
- Then remove the temporary archive from the server.
Recommended procedure for uploading and extracting #
- Check the content and directory structure of the ZIP archive.
- Open the correct destination directory in the file manager.
- Back up existing productive files in case they might be affected.
- Upload the ZIP archive.
- Mark the archive and select Extract.
- Check the destination path.
- Start the extraction.
- Then check the directory structure.
- Test the website or the affected feature.
- Delete the ZIP archive when it is no longer needed.
Basic rule: When unpacking, two things are crucial: What is in the archive? and Where will it be extracted to? Check both before you start the extraction.
When should you contact support? #
If an archive cannot be created, uploaded, or extracted and the cause is unclear, note the displayed error message.
For an analysis, the following information is particularly helpful:
- affected domain
- Name of the archive
- approximate size of the archive
- Source or destination directory
- what action should be performed
- displayed error message
- whether the website shows an error after unzipping
Do not share passwords or other access credentials within a standard error description.
Summary #
With the cPanel File Manager, you can compress files and folders directly on the server as a ZIP archive and extract existing ZIP files again.
To create, you select the desired data, choose Compress and create a ZIP archive. If you want to download it as a backup, then check on your computer whether the file can actually be opened.
When extracting, you should pay special attention to the contents of the archive, any additional main folder that may be present, and the selected destination directory. If files with identical names already exist there, they may be overwritten by the extracted files.
Do not leave full website archives lying around unnecessarily in publicly accessible directories and remove temporary ZIP files after completing the work.
Also note that a ZIP archive of the website files does not yet constitute a complete website backup in the case of database-driven applications such as WordPress.
