The file manager in ISPmanager is the quickest way to work with your site's files. It runs in the browser, needs no extra software and covers most of what people normally do over FTP: small edits, uploading images, extracting archives and fixing permissions.
Opening it and finding your site
The file manager is in the panel's left menu and opens in your hosting user's home folder. Sites usually live under www, one folder per domain, such as www/misol.uz. That folder is the site root: a request for misol.uz/menu.pdf is served from menu.pdf inside it. The path bar at the top lets you jump back up. Dotfiles like .htaccess are shown too, which matters because redirects and security rules live there.
Example: updating a restaurant menu
A family restaurant in Andijan updates its menu every season. The manager needs to publish a new PDF menu and dozens of dish photos and remove the old ones, without calling a developer. Everything below follows that job from start to finish, and the whole task fits comfortably into a few minutes once you know where each action lives in the file manager's menu.
Uploading
Open the target folder, click upload and pick files. For dozens of photos, zip them on your computer, upload the single archive and extract it on the server; it is much faster. Upload size may be limited, so very large archives are better sent via FTP or SSH. Avoid spaces, Cyrillic and special characters in file names: use menyu-2026.pdf, not Yangi menyu 2026.pdf. Linux is case-sensitive, so Rasm.JPG and rasm.jpg are different files.
Archives
Select an archive and extract it; zip and tar.gz are supported. Check the archive structure first: an extra top-level folder leaves files in www/misol.uz/rasmlar/rasmlar/, and you will need to move them up. You can also select files and create an archive, a quick way to back up a folder, for example rasmlar-eski.zip before deleting old photos.
Editing in the browser
PHP, HTML, CSS and .htaccess files open in the built-in editor. To force HTTPS, for example:
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [L,R=301]
Copy the file to .htaccess.bak first, because a single mistake there returns a 500 error for the whole site. Save files as UTF-8 without BOM; a BOM at the start of a PHP file can trigger "headers already sent" warnings and odd characters at the top of the page.
Permissions
| Item | Mode | Meaning |
|---|---|---|
| Regular files | 644 | Owner writes, others read |
| Folders | 755 | Owner writes, others can enter |
| Secret config | 600 or 640 | For example, a file with the database password |
Never use 777; on hacked sites, malicious code lands in exactly such folders. When a plugin cannot write to a folder, the cause is usually file ownership, not permissions. Files uploaded through the file manager already belong to the site user.
Moving and deleting
Moving, copying and renaming take a couple of clicks. Deleting deserves care: there is usually no recycle bin, so archive important folders first or make sure a recent backup exists before you confirm. On sayt.uz hosting, you can open a support ticket from your account if you need a restore from backup.
When it is not enough
Moving a multi-gigabyte site, searching text across thousands of files or running WP-CLI calls for SSH, and regular syncing works better with FileZilla or WinSCP. For the restaurant manager, though, the file manager is all that is needed: upload the new menu, archive the old one, done in minutes.