Website files

How to use Plesk File Manager

Upload, edit, organise and archive website files in your browser without an FTP application, while protecting the live site from accidental changes.

Document rootEdit the correct website
Before editingCreate a backup
Large uploadsArchive and extract

Make a recovery copy before editing a live file

Download the file, copy it with a recognisable backup name, or create a Plesk backup before a larger change. File Manager saves directly to the live hosting account and has no universal undo button.

Find File Manager and the document root

  1. Open My Services, choose the hosting service and select Log in to Plesk.
  2. Under Websites & Domains, find the intended domain and select File Manager.
  3. Confirm the hosting document root in Hosting Settings if several domains share the subscription.
  4. Open that directory before uploading or editing the website.

Common roots include `httpdocs` or a domain-specific folder, but the value shown in Hosting Settings is authoritative for that website.

Work with files and folders

Upload
Add one or more files to the current directory.
Edit
Change a text-based file such as HTML, CSS or configuration.
Copy or move
Duplicate a file for backup or reorganise content.
Rename
Change a filename without editing its contents.
Archive
Compress files for download or extract an uploaded package.
Remove
Delete selected content after confirming it is not required.

Upload a website as an archive

  1. Create a ZIP archive on your computer with the website files at the archive's top level.
  2. Upload the ZIP to the intended document root.
  3. Select the archive and choose Extract Files.
  4. Check that the homepage file is in the root rather than inside an unwanted extra folder.
  5. Test the website, then remove the uploaded ZIP so it cannot be downloaded publicly.

Hidden files and permissions

Files such as `.htaccess` can control redirects, access and PHP behaviour. Make a copy before editing them and confirm File Manager is configured to show hidden files if one appears missing.

Avoid making files or folders world-writable. Use the existing permissions as your guide and change them only when a trusted application specifically requires it. Ownership problems are better repaired through Plesk or UKC support than by applying broad permissions.

Check the public result

  • The intended page loads over HTTPS.
  • Images, style sheets and scripts load without browser errors.
  • Forms, login and other important workflows still operate.
  • Temporary archives and backup files are not publicly accessible.

A file change caused an error?

Restore the backup copy if possible. If help is still needed, send the domain, changed file path, time of the change, exact browser error and relevant log lines. Never send Plesk, FTP or database passwords.

Ask the Hosting team

Was this answer helpful?

« Back