Organise your directories, adjust security settings, and clear out legacy content natively on your server using client shortcuts in WS_FTP.
Managing your website files correctly helps keep your hosting environment organised, secure, and running smoothly. Whether you’re maintaining a personal website or managing multiple client sites, understanding these basic file management tasks can save time and reduce the risk of website issues. This guide will help you manage files and folders in WS_FTP while connected to your 1-grid hosting account. You’ll learn how to create new folders, rename existing folders, delete files and directories you no longer need, and change file permissions.
Before You Begin
Before reorganising your remote server directory layouts inside WS_FTP, make sure you meet the following baseline requirements:
- The WS_FTP software client is running on your local computer device.
- You have an active connection mapped via Configure WS_FTP for your 1-grid Hosting Account.
- An FTP user profile that holds full read/write administrative permissions for your target hosting paths.
💡 Context: WS_FTP is an FTP (File Transfer Protocol) client that allows you to securely connect to your 1-grid hosting account and manage the files stored on your web server. 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
- Open WS_FTP and establish an active connection to your hosting account profile card.
- In the remote server explorer pane view, browse to the exact parent location where you want to drop a new directory tree.
- Enter an alphanumeric name for the new folder and confirm the prompt action. Your new folder will appear in your current directory listing immediately.
2. Rename a Folder
- Locate and highlight the specific target folder or file row item you want to modify on the remote server window list.
- Enter your updated folder name string details and click Save to apply changes. The folder name will update across your network environment immediately.
3. Delete a Folder or File
- Select the folder or file item row, and click the Delete cross icon in the toolbar strip.
- Confirm the system verification pop-up box prompt to permanently drop the assets from your web disk allocation space.
4. Change File Permissions
- Select the specific configuration file or data wrapper layout whose directory attributes require tuning.
- Update the required access checkboxes or attribute fields to match your specific application requirements.
- Save your changes to apply the updated system state rules to the server.
What Happens Next?
Once file and directory properties are saved inside the WS_FTP workspace panel, server configuration rules 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 and nested contents from the host disk sector.
Important Things to Know
- The Permission Lockdown Rule: Setting overly loose structural settings like
777bypasses 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.phpto 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 Upload and Download Files Using WS_FTP 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 or system directories 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.
- Setting overly permissive access states (such as
777) unnecessarily, exposing server files to script injections. - 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, try reconnecting to your hosting account and refresh your active session logs to clear out local cache parameters.
You’re Ready!
Your remote server file environment cleanup is completed. Maintaining a secure, clean, and organised directory tree hierarchy prevents systemic storage conflicts and keeps your web environment operating efficiently.
Related Articles
Need Help?
If WS_FTP blocks directory modifications with critical socket failures or security error logs, contact us. Our Support Team is ready to offer support and guidance.
Before submitting a request, please prepare:
- Your primary domain name and hosting service plan metrics.
- The exact path of the target file or folder directory you are modifying.
- The complete text string configuration of any error messages displayed on your screen console.
- A screenshot of your WS_FTP workspace window view showing the failure notice.