TSI x DigitalOceanDocumentation
Documentation sectionsBrowse
HomeDocsFile Manager

Customer documentation

File Manager

Use cPanel File Manager safely: understand public_html, document roots, uploads, permissions, and common file problems.

Files and document roots

Most simple cPanel sites serve files from public_html. Addon domains and subdomains can use different document roots, so confirm the domain mapping before replacing files.

  1. 1Open cPanel and choose File Manager.
  2. 2Open public_html for the primary domain, or the configured folder for an addon domain or subdomain.
  3. 3Upload or edit files only in the folder that belongs to the domain you are changing.
  4. 4Keep a backup before replacing an existing site.
  5. 5Clear application, browser, or CDN cache if old content still appears after the upload.
File safety
Do not delete unfamiliar folders from the account root. If you are unsure whether a folder is active, open a ticket with the domain and folder path.

Upload workflow

File Manager is the simplest way to upload a small site or replace a few files. For larger sites, FTP or a migration process may be more reliable.

  1. 1Back up the existing site files before replacing anything.
  2. 2Open the correct document root for the domain.
  3. 3Upload the new file or ZIP archive.
  4. 4Extract archives only inside the intended document root.
  5. 5Confirm index.html, index.php, or the app entry file is in the correct folder.
  6. 6Load the site in a private browser window and clear cache if old content still appears.

Edit files safely

File Manager can edit text-based files directly in the browser. Use this for small changes only. For bigger changes, edit locally, test, then upload the finished file.

  1. 1Download the file before editing so you have a copy to restore.
  2. 2Open the file in File Manager and choose Edit or HTML Editor only when you know what kind of file it is.
  3. 3Make the smallest possible change and save.
  4. 4Reload the site in a private window to confirm the change.
  5. 5If the site breaks, restore the downloaded copy or undo the exact edit.
Safe to edit carefully
HTML, CSS, JavaScript, .htaccess, robots.txt, small config files, and simple text files.
Do not edit blindly
Binary files, images, archives, large generated files, unknown framework build files, or database exports.
WordPress caution
Back up wp-config.php, theme files, and plugin files before touching them. A typo can take the site down.
Encoding
If strange symbols appear after saving, restore your backup and edit locally with a proper code editor.

ZIP files and extraction

Uploading a ZIP and extracting it on the server is faster than uploading hundreds of small files. The important part is extracting into the correct folder.

Upload archive
Upload the ZIP into the document root or a temporary folder inside the account.
Extract
Use Extract in File Manager and confirm the destination path before continuing.
Nested folder problem
If the ZIP creates an extra folder, visitors may see a blank or old site. Move the contents into the actual document root.
Clean up
Delete the ZIP after extraction if it contains source files, configs, or private project material.
Restore
If the extracted files are wrong, remove the new files and restore the backup copy.

Common file areas

public_html
Default document root for many primary domains.
Addon domain folders
A separate folder may serve each addon domain. Confirm the mapping before editing.
Subdomain folders
Subdomains can point to their own folders, often named after the subdomain.
wp-config.php
Common WordPress configuration file. Back it up before editing.
error_log
Application or PHP errors may appear here when the site fails.
.htaccess
Can control redirects, rewrites, PHP behavior, and access rules. Small mistakes can break a site.

Permissions and edits

Permissions determine whether the web server can read or run files. Avoid changing permissions broadly unless support asks you to.

  • Download a copy before editing important config files.
  • Do not delete unfamiliar account-root folders.
  • Avoid setting folders or files to fully public write permissions.
  • If a change breaks the site, restore the previous file or open a ticket with the exact path you changed.

Permission reference

File permissions are shown as read, write, and execute permissions for owner, group, and public. The cPanel File Manager permissions tool lets you change these, but broad public write access is rarely appropriate.

0644
Common default for normal files. The owner can write; visitors can read served files.
0755
Common default for folders and executable directories. The owner can write; the web server can enter the folder.
0700
Private directory style permission. Use only when a tool or support specifically asks for it.
0777
Avoid this. It allows broad write access and can create security problems.
After changing
Reload the site and check logs. If the site breaks, restore the previous permission value.

File Manager troubleshooting

Wrong page loads
Confirm files are in the document root for the domain visitors are using.
403 Forbidden
Check index file presence, folder permissions, and access rules.
500 error
Check .htaccess, PHP errors, plugin changes, and error_log.
Old content appears
Clear browser, app, plugin, or CDN cache.
Upload fails
Check file size, storage usage, archive format, and whether the connection timed out.