Skip to content

File Manager

Upload, edit, organize, and set permissions on website files.

1Overview

File Manager works inside your hosting account and exposes the files used by your websites, including public_html and application directories allowed by the panel.

File Manager in the user panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.
File Manager showing account folders, location shortcuts, upload and creation controls, and file action menus.

File Manager in the user panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.

2Before you begin

User-panel actions affect only resources owned by the signed-in hosting account.

3Step-by-step workflow

Open File Manager, select the correct website root, upload files or create folders, use the editor for small text changes, and set sensible ownership and permissions through the provided controls.

  1. Open File Manager and choose Home, Websites, Applications, Mail, or Backups as appropriate.
  2. Open the intended site directory and check the current path before selecting files.
  3. Use New folder or New file for a small addition, or Upload to transfer existing files.
  4. Open a text file in the editor, make the required change, and save it after retaining a copy.
  5. To move items, select the files or folders and choose Move selected, then choose the destination within your account.
  6. To create an archive, select the required items, choose Compress selected, and select ZIP or TAR when offered.
  7. Review destination names and any overwrite prompt before confirming a move, upload, or extraction.
  8. Refresh the destination folder and check the website or application after the change.

4Practical example

Example: select a staging folder and compress it as a ZIP before replacing its content. To move a file into another folder, use Move selected rather than downloading and uploading it again.

5Choosing a safe archive or move destination

Use a new archive name and keep private backups outside the public website directory. An archive stored inside a public document root may be downloadable by visitors. Compression needs working space as well as room for the finished archive.

Moving a file changes its path. Before moving application files, check links, uploads, configuration references, and scheduled jobs that use the old location. Extract unfamiliar archives into a new empty folder so you can review their contents before moving them into a live site.

6Verify the result

Validate the outcome from the affected website, mailbox, application, or client connection after the panel reports success.

  1. Request the changed website path in a browser.
  2. Check the file list, permissions, and error log if the site returns an error.

7Common problems and what to check

The destination is refused: it may be outside your allowed account path or lack the required access.

An archive fails to create: check available disk space, file access, and the selected output name.

The website breaks after a move: restore the original paths and check application references; moving a whole document root can require a separate website setting change.

8Security, impact, and rollback

Upload to the domain document root, not an unrelated directory. Take a backup before replacing a production configuration or deleting a directory tree.

Related guides

Backup & RestoreCreate and restore account-level backups.DatabasesCreate databases, users, backups, and phpMyAdmin access.See all guides in User hosting panel

Still need a hand?

Get help with your plan, website, or hosting through your client area.

Open client area