Quick answer
Renaming a remote folder can break URLs, document-root mappings and application paths. Record the old path and verify dependencies before changing the name.
Applies to
For FileZilla Client on your own computer and an authorized Interactive Online hosting login. Our file-transfer workflow uses SFTP over SSH; FTP access is retired. Select SFTP, use the assigned server and SSH port, and authenticate as the eligible cPanel account with an authorized key. Legacy FTP-only subaccounts cannot sign in to SFTP. Check the connection guide for your server and port.
Steps
- Confirm the server and full remote folder path, then preserve a recovery copy of the affected files and domain-to-folder mappings.
- Use the remote folder's Rename action and enter the intended name. Account for case sensitivity on the hosting filesystem.
- Update dependent paths only as part of the planned change. Be ready to restore the previous name if the site stops finding its files.
Check the result
Check the remote listing, website URLs and any application paths using that directory.
Troubleshooting and support
If the folder serves as a domain's document root, coordinate the mapping instead of assuming a rename moves the public site automatically.
If the problem continues, contact support from the account that owns the service. Include the domain, exact error, time and time zone, tool name, and a redacted screenshot. Keep passwords, private keys, cookies and private message content out of the ticket.
Video tutorial
The original video is preserved. Its interface or product version may differ from the written guidance above.
Related help
- Upload a reviewed file with cPanel File Manager
- Find the correct document root before an AI tool uploads files
- Import and authorize a public SSH key in cPanel
Official references
Written content reviewed November 1, 2026. Menu availability depends on the product version, permissions and service.