Manage Website Files and Folders in FileZilla for Your 1-grid Hosting Account

Organise your directories, adjust security states, and clear out legacy content natively on your server using command shortcuts.

Whether you’re organising your website, cleaning up old content, or updating file permissions, FileZilla provides an easy way to manage your hosting files securely. This guide will help you manage your website files and folders using FileZilla with your 1-grid hosting account. By the end of this guide, you’ll be able to create, rename, and delete folders, as well as update file permissions with confidence on your 1-grid Client Portal account.

Manage Website Files and Folders in FileZilla | 1-grid

Table of Contents

Before You Begin
Follow These Steps
What Happens Next?
Important Things to Know
Common Mistakes to Avoid
If This Didn’t Work
You’re Ready!
Related Articles
Need Help?

Before You Begin

Before reorganising your remote directory structures inside FileZilla, make sure you have:

The FileZilla Client application active on your computer device.
Established a live connection block to your server node via How to Set Up FileZilla for Your 1-grid Hosting Account.
An FTP user profile that holds administrative write permissions for your target hosting paths.

💡 Context: FileZilla acts as a direct command mirror tool. Every file creation, directory label rewrite, or security mode flip you execute inside its control pane updates the active files resting on your web storage platform in real-time.

Follow These Steps

1. Create a New Folder

Step 1: Look to the right-hand Remote Site panel layout area. Double-click through the file paths to navigate to the exact sub-folder where you want to drop a new directory tree.
Step 2: Right-click inside any empty white space layout zone inside that directory grid explorer pane and select Create directory.
Step 3: Type a clean, concise, alphanumeric folder name into the prompt field window, and click OK. Your fresh directory item row will map instantly onto the grid.

2. Rename a Folder

Step 3: Locate the target folder or deployment script line item inside your remote explorer listing window.
Step 4: Right-click the folder name string and select Rename (or highlight it and press F2 on your keyboard). Type your updated text string details and press Enter to save.

3. Delete a Folder or File

Step 5: Navigate to the obsolete resource file or directory asset you intend to wipe.
Step 6: Right-click the item row and select Delete. Confirm the system verification pop-up box to permanently drop the assets from your web disk allocation space.

4. Change File Permissions

Step 7: Locate the core configuration script file or data wrapper layout whose directory attributes require tuning. Right-click the item and select File permissions… from the context menu.
Step 8: Check the appropriate Read, Write, and Execute checkboxes (or type the precise three-digit numeric access value, such as 644 for files or 755 for directories), and click OK to run the deployment script.

What Happens Next?

Once adjustments are committed inside the FileZilla workspace panel, server rule definitions cycle instantly.

Real-Time Property Flips: Folder renames or permission adjustments modify your application connection routing immediately.
The Permanent Purge Effect: Dropped directory units bypass any localised desktop recycle bins, completely purging files from the host disk sector.

Important Things to Know

The Permission Lockdown Rule: Setting overly loose structural numbers like 777 bypasses vital web host defences. Keep backend application codes restricted to a safe file permission baseline of 644 for scripts and 755 for directories.
Landing Page Overrides: If you rename or tamper with your primary landing indicators (e.g., changing index.php to uppercase formats), web browsers will fail to resolve your landing templates, throwing immediate HTTP 403 errors.
Backup Priority Protocol: Always pull down a standalone folder download copy of your core public folder arrays via How to Upload and Download Files Using FileZilla before executing multiple batch folder deletes.

Common Mistakes to Avoid

Accidentally highlighting and deleting nested framework folder units while executing directory cleanups.
Renaming standard operational engine folders that active platform plugins rely on for loading processes.
Applying incorrect, restrictive permission keys that lock out your own application’s web server engine from reading its text settings files.
Tweaking massive directory trees recursively without testing individual page performance first.
Presuming system updates failed when your desktop browser interface is simply pulling an old, un-cleared page cache.

If This Didn’t Work

Should the status panel console box output permission exception alert codes or file locking warnings during execution, verify your FTP account profile holds full write permissions. If folder name renames refuse to register inside your browser views, right-click inside the remote explorer block and select Refresh to clear out local cache logs.

You’re Ready!

Your remote server file environment cleanup is completed successfully. Maintaining a secure, clean, and organised directory tree hierarchy prevents systemic storage conflicts and keeps your web environment operating efficiently.

Log In to Customer Zone & Manage FileZilla Folders Now

Need Help?

If FileZilla blocks directory modifications with critical socket failures or security error logs, contact us. Our Support Team is ready to offer support and guidance.

Before launching a request, please prepare:

Your primary domain name and hosting service plan metrics.
The exact path layout of the target file or folder directory you are modifying.
The complete text string configuration of any error messages displayed on your screen console.
The specific numeric permission code value you were trying to apply.

Updated on August 21, 2026

Was this article helpful?

Yes No