Obtain the archive from a trusted source, inspect its contents and confirm enough free space for both compressed and extracted data. Back up existing destination files before deploying anything over them.

1. Open File Manager, choose the intended domain and select Login. Use a private staging directory outside the served document root when your account permits it. If the tool only exposes a public location, use an access-restricted temporary folder and verify that restriction before uploading. Do not stage an archive containing secrets where visitors can download it.
2. Upload or locate the ZIP archive and open its details. Review the displayed entries and whether they contain an extra top-level folder.
3. Use Unzip to Folder for a separate destination where available, or confirm the folder that the normal Unzip action will create.
4. Inspect extracted files before moving them into production. Check the document root, hidden configuration files, permissions and application dependencies.
5. Test the deployed application, then remove any publicly reachable archive and temporary extraction copies once recovery copies are safely stored elsewhere.

The expected file tree should exist in the intended location without an accidental extra directory in the public URL or overwritten configuration.

Archive support and behaviour depend on the installed Tiny File Manager version. If extraction fails, keep the original archive and use an approved alternative rather than repeating a partially destructive extraction. Large archives can exceed storage or runtime limits.

No. An archive may contain a database export, but restoring that data and connecting the application are separate steps that must match the files’ recovery point.

• Changing SiteWorx file permissions for a specific application
• Changing a SiteWorx subdomain’s document root
• Scheduling SiteWorx backups with retention
• Changing a SiteWorx database-user password

• InterWorx: How To Extract A Zipped File Tiny Filemanager