Upload, edit, and organise your website data directly inside your browser without installing external FTP software.
This guide will help you use File Manager in cPanel to upload, edit, organise, and manage your website files directly from your hosting account. Whether you need to update website content, upload images, edit configuration files, or adjust permissions, File Manager provides a simple way to manage your website without installing additional software. Most file management tasks can be completed directly in cPanel, making it one of the quickest ways to maintain your website on your 1-grid hosting account.

Before You Begin
Before diving into your server’s directory layout, make sure you have:
- Access to your 1-grid Customer Zone
- An active web hosting package running a cPanel dashboard
- The core website content and configuration files you want to deploy or update
💡 Context: File Manager is a built-in browser tool within cPanel that allows you to manage files and folders stored on your hosting account. For most website owners, File Manager offers a much simpler, faster alternative to installing and configuring external FTP software.
Follow These Steps
1. Open cPanel
Log in to your 1-grid Customer Zone, locate the web hosting service you want to manage, and select Login to cPanel to launch your hosting dashboard.
2. Open File Manager
Navigate down to the Files section block and click File Manager to initialise the web-based file tree system interface.
3. Understand the File Manager Layout
The dashboard layout splits cleanly into two primary administrative interaction areas:
- Left Panel: Displays the overall tree folder structure of your hosting directory system.
- Right Panel: Displays the specific nested file list inside whichever folder is currently selected.
Directory Map Guide:
public_html→ The main target directory for all live public website files.www→ A direct operational shortcut link pointing straight topublic_html.mail→ Storage mapping directories for internal account email logs.logs→ Text archives compiling server and site user interaction statistics.tmp→ Temporary structural cache files generated by web scripts.
4. Upload Files
Double-click and open the target destination folder (typically public_html). Click the Upload button from the top toolbar menu, select or drag-and-drop the files from your computer, wait for the progress bar to reach 100%, and close the upload tab to see your new assets listed in the directory folder.
5. Create a New Folder
Click the + Folder icon button in the top menu layout. Type in your preferred folder directory name, confirm the target directory location path, and select Create New Folder to establish the directory block immediately.
6. Create a New File
Click the + File link icon in the top header action strip. Input your exact file script name (e.g., test.php), specify the destination directory path layout, and click Create New File.
7. Edit a File
Highlight the specific text or configuration file row entry in the file explorer. Click the Edit or Code Editor button from the top panel strip, make your explicit text string modifications, and select Save.
8. Change File Permissions
Select any file or folder asset row, and click the Permissions key icon button in the header toolbar menu. Check the option boxes to match your script guidelines and click Save.
- Standard Files Baseline: Set to file permission layout 644
- Standard Folders Baseline: Set to folder directory layout 755
9. Delete Files or Folders
Highlight the unwanted item row, click the Delete cross icon in the menu bar, confirm the pop-up warning criteria prompt, and choose whether to send it to the trash interface or skip the bin path entirely.
What Happens Next?
Once changes are processed inside the manager, they execute across the infrastructure instantly.
- Live Updates: Saved edits, added code pages, or fresh directory paths update your active URL behaviour on the spot.
- Validation Loop: Open your site domain index route in an external private tab window to confirm that fresh asset scripts render flawlessly.
Important Things to Know
- Immediate System Updates: Edits saved via the Code Editor update file strings in real-time, removing the traditional delay found in uploading files via basic connection networks.
- The Critical Drop Threat: Purging directories or misconfiguring underlying settings permanently can cause immediate broken theme dependencies or break your website’s database layout connections.
- The Permission Lockdown: Opening up file blocks to open permissions like
777bypasses vital internal hosting server protections, leaving folders highly exposed to script injections. Keep files locked down to the standard644level.
Common Mistakes to Avoid
- Uploading asset zip containers or media indices outside of the primary
public_htmldirectory container root. - Applying open, overly permissive attributes such as
777to critical code scripts during standard maintenance loops. - Updating runtime configuration variables inside system text profiles without making a copy backup file first.
- Dropping legacy core folders or cleaning folder zones without knowing what functions they run.
- Disconnecting transmission streams or pushing files before files fully finish processing through the upload loader widget.
If This Didn’t Work
Should files fail to complete processing or throw disk error warnings during upload phases, confirm your storage metrics by reviewing your hosting account space levels. If code modifications apply successfully inside the editor but refuse to register inside your browser, check your localised client network and cache rules first.
You’re Ready!
Your master file explorer environment is fully mapped out. Mastering browser-based file manager operations gives you the ultimate control to securely adjust, deploy, and organise your web content platform without relying on third-party software.
Related Articles
Need Help?
If your file manager fails to create directories, blocks code alterations with systemic firewall errors, or throws folder permissions blocks, contact us. Our Support Team is ready to help.
To ensure our engineering teams can inspect your directory environment quickly, please provide:
- Your primary domain name and active web hosting account selection
- The explicit target file system path involved in the fault
- A screenshot of your File Manager interface view showing the conflict
- The complete text configuration of any error messages displayed on screen
- A concise log entry description detailing the exact task you are executing