Our Account Manager includes file tools for supported Web Hosting accounts, allowing you to browse folders, upload files, read and edit text, create folders, and perform supported copy, move, archive and trash operations. These controls are useful for publishing a small website, inspecting a configuration file or replacing an application asset without opening a separate desktop program. Available operations follow the account's permissions and hosting configuration.
IN THIS ARTICLE
01 Choose the correct folder before uploading
Begin by confirming the target website's document root. A hosting account can contain several websites, email data, backups and system-managed folders, so the first folder you see is not necessarily where a particular site's public files belong. Upload a new website into the intended location, inspect archive contents before extraction, and check that an archive does not create an extra directory level that hides the expected home page.
02 Edit and deploy changes with a recovery plan
- Before editing an existing application file, preserve its current version and understand how you will restore it.
- Make one focused change, save it and test the affected page or function.
- For larger deployments, use a versioned release process or another suitable transfer method provided for your account.
Do not assume that a file upload automatically runs dependency installation, database updates or other application deployment steps.
Use permissions that suit the application and server environment. Making every file or folder writable is not a sound way to resolve an access problem and can expose the account unnecessarily. Keep database credentials and private configuration out of public downloads, and avoid storing backup archives in a publicly accessible website folder. Trash recovery is useful only while the item remains recoverable; permanent deletion and an emptied trash may require a separate backup. Check the selected path carefully before any operation affecting multiple files.
Why might an uploaded file not appear at the expected URL?
Check whether the file is in the wrong document root, inside an extra enclosing folder created by extraction, or saved with a different letter case from the requested URL. Compare the domain's configured folder with the actual file path before moving or overwriting anything. Preserve an existing file before replacing it, then test the affected URL. Remove temporary public test files and exposed archives afterward.
File changes alone may not complete an application release. Dependencies, database migrations and process restarts can still be required. An account file tool is also not an automatic version-control system: keep a suitable release or backup process for changes that must be recoverable.