Even after launching flexible pay-as-you-go site plans, a streamlined dashboard, and simplified site management tools, InstaWP isn’t slowing down. It’s back with a powerful new upgrade; Local Mount.
This feature lets you access and edit your cloud-based WordPress site as if it were a folder on your local computer. No more back-and-forth with FTP or zip files. With Local Mount, your InstaWP site’s files live right inside your file explorer, ready for real-time editing.
It’s a game-changer for agencies and developers who want a seamless bridge between cloud-based workflows and local development environments.
Table of Contents
What Is the Local Mount Feature?
The Local Mount feature in InstaWP lets you access your cloud WordPress site’s files directly from your local computer; as if they were stored in a folder on your hard drive.
Think of it like this: instead of logging into cPanel, downloading files, or using FTP to make edits, you simply mount your InstaWP site to your local system (Windows, macOS, or Linux).
Once connected, your site’s file structure (like wp-content, wp-config.php, and theme/plugin folders) appears in your file explorer; ready for real-time editing.
This means:
- You can open your site in VS Code or any editor.
- Save changes instantly, no uploading required.
- Work faster on themes, plugins, and custom code.
- Stay cloud-first while developing locally.
In short, Local Mount feature of InstaWP turns your cloud site into a locally editable project, giving you the speed of local WordPress development with the convenience of InstaWP’s managed cloud hosting.
Why We Came Up With Local Moun Feature?
Many InstaWP users wanted the best of both worlds, the ability to access their WordPress site locally while still enjoying the speed, simplicity, and flexibility of cloud-based development.
Why? Because some projects demand local access for things like:
- Theme and plugin development: Developers often need to make rapid file-level changes, test custom code, or debug issues directly within wp-content folders.
- Real-time testing and prototyping: Editing files in a local IDE (like VS Code) while seeing changes live in the browser speeds up the dev loop dramatically.
- Bulk file operations: Tasks like uploading large assets, restructuring theme folders, or managing multiple templates are easier with local drag-and-drop.
- Version control integration: Many teams prefer working in a local Git repository for source control, which requires access to actual site files.
- Better tool compatibility: Linting, formatting, and search tools work more reliably and quickly on local file systems compared to cloud-based editors.
- Collaborative development: In agency setups, multiple devs might need access to the same site. Mounting the same cloud site locally ensures everyone works in sync without stepping on each other’s toes.
We wanted to make sure our users with these specific requirements don’t feel that their hands are tied. So, one fine day, our developers decided to cater to them, and this is how Local Mount came into being.
What Does the Local Mount Feature Do?
InstaWP’s Local Mount feature makes you more powerful and efficient as a WordPress developer. With this, you can:
- Mount a Remote Site Locally: Local Mount links your remote InstaWP site’s file storage to a directory on your computer. Once enabled, the WordPress site’s files appear in your File Explorer (Windows) or Finder (Mac) as though they are on a local drive. You can open, edit, copy, or delete these files using familiar desktop tools.
- Do real-Time File Sync: Changes you make to these files on your computer are immediately reflected on the cloud site. This eliminates the need to manually upload files after editing; no more using separate FTP clients or zipping files to move them. It streamlines development by keeping the local and cloud environments in sync.
How Does Local Mount Work?
Local Mount leverages standard network file sharing protocols (under the hood, it uses a secure WebDAV/SFTP connection) to expose your site’s filesystem. When you enable the feature for a site, InstaWP provides a Server Address (URL) along with a Username and Password. Your operating system uses these credentials to mount the remote directory:
- On Windows, the remote site is mapped as a network drive. Windows treats the provided URL as a network location and, after authentication, displays the WordPress file system as a new drive letter under “This PC.”
- On macOS, the remote site is mounted as a network volume. Using Finder’s “Connect to Server” feature with the InstaWP address will attach the site’s files under the Locations section in Finder (after you enter the credentials).
- On Linux, you can use similar methods (for example, many Linux file managers have a Connect to Server option supporting FTP/WebDAV/SFTP; or you can use sshfs from the command line) to mount the InstaWP site’s file system into your local filesystem. This gives Linux developers the same seamless access.
Behind the scenes, the InstaWP platform is serving your site’s files over a secure connection for your OS to mount. You are not running WordPress locally; the WordPress site still executes on InstaWP’s servers, but you can manipulate the files as if they were local. This is ideal for editing theme files, plugin code, or configuration files quickly from your favorite code editor on your computer, while the site runs in the cloud.
How You Can Use Local Mount Feature of InstaWP
Using the Local Mount feature on InstaWP takes just a few clicks; no technical gymnastics required. Like everything else in InstaWP, it’s built to be fast, intuitive, and hassle-free.
Before you begin, make sure you have the following:
- An active InstaWP site
- A stable internet connection
- A Windows system with the WebClient service running (enabled by default)
- Admin access on your PC (needed to map network drives)
- A site plan that supports Local Mount (available from Sandbox plan and above)
Once these are in place, you’re ready to mount your InstaWP site like a local folder and start editing like a pro. Next, we will talk about activating Local Mount in MacOS, Windows, and Linux.
How to Enable Local Mount Feature on InstaWP
This video will bring more clarity on how to use Local Mount on MacOS.
To enable Local Mount on your InstaWP dashboard, you need to go to the dashboard and select the site for which you want to enable this feature.
As you access the site’s settings, you will be able to view the Local Mount feature on the left side of the panel. Click on it and toggle the Enable Mount option.
Once toggled, InstaWP will display the connection details – specifically a Server Address (URL) for the mount, along with a Username and Password to authenticate the connection.
How to use Local Mount on macOS
Next, follow these steps to use the Local Mount on MacOS to access your WordPress site locally.
1. On a Mac, open Finder, then click the Go menu and select “Connect to Server” option to open a server connection dialog.
2. In the Connect to Server dialog, input the Server Address URL provided by InstaWP for your site. Add https:// before the server address. Click Connect.
3. You will be prompted to enter the Username and Password from the InstaWP Local Mount details. Provide those credentials and confirm to connect.
Once connected, the WordPress site’s folder will be mounted on your Mac. It should appear in Finder, under the Locations sidebar, as a network drive or folder (often with the site name or address).
You can click it to browse and open files. At this point, you can edit the site’s files using local applications (e.g., a code editor), and all changes will apply to the remote site instantly.
How to use Local Mount on Windows
Here is how you can use Local Mount on Windows to access WordPress site locally.
1. On your Windows PC, open This PC (File Explorer). In the top menu, click “Map Network Drive.” (You can also right-click on “This PC” and choose Map Network Drive.) This opens the Map Network Drive wizard.
2. In the Map Network Drive dialog, choose a drive letter (or leave the default). In the “Folder” field, paste the Server Address provided by InstaWP for the site.
Windows will prompt for network credentials. Enter the Username and Password from the InstaWP Local Mount info. (These were shown in the InstaWP dashboard when you enabled the toggle.) If desired, check “Remember my credentials.” Click OK to connect.
4. After a moment, the network drive connects. Your InstaWP site now appears as a new drive under “This PC.” You can open this drive to browse the WordPress files (wp-content, wp-admin, etc.) just like a local folder.
How to use Local Mount on Linux
You have two ways to access your WordPress site locally on a Linux system.
Via File Manager: If you use a desktop environment like GNOME or KDE, their file managers have a “Connect to Server” feature. For example, in GNOME Files (Nautilus), you can enter the InstaWP Server Address (prefixed with a supported protocol like dav:// or sftp://) and then provide the Username/Password when prompted. This will mount the remote WordPress directory so it appears in your file manager, just like on Windows/Mac.
Via SSHFS: Alternatively, Linux developers can use the sshfs command-line tool to mount the remote file system. InstaWP provides SFTP/SSH credentials, so using sshfs user@host:/remote/path /local/mountpoint (substituting the InstaWP user, host, and mount path given in the Local Mount info) will attach the site’s files into a local directory.
Once mounted on Linux, the experience is the same; you can navigate into the mounted folder and edit files directly. The specific steps can vary by Linux distro, but the key point is that InstaWP’s Local Mount supports any method that can use SFTP/WebDAV credentials to map a remote folder locally.
What Value Local Mount Feature Will Bring for Developers & Agencies
The Local Mount feature is designed to improve development workflows. Here are the key benefits it offers for WordPress developers and agencies:
- Faster Development Iterations: No more manual file transfers – edit files in your code editor and save. The changes reflect on the cloud site immediately. This speeds up the tweak-test cycle when building or debugging a WordPress theme or plugin.
- Use Local Tools on Cloud Sites: You get the convenience of local development (using your preferred IDE, editor, or search tools on your desktop) while still running the site in the cloud.
For example, an agency developer can open the remote site’s theme folder in VS Code or PHPStorm and leverage features like search/replace across files or version control, without setting up a local LAMP stack.
- No Local Server Needed: It eliminates the need to set up a full local WordPress environment for testing. This is especially valuable for quick sandbox testing or for team members who may not have a powerful PC.
The WordPress instance runs on InstaWP’s servers, but feels local for file operations. It’s a hybrid approach combining cloud hosting with local editing.
- Collaboration and Onboarding: Because the site is cloud-hosted, it can be shared via URL or handed off, but each developer can mount it locally to work on files. This is useful for agencies where multiple developers might need to inspect or modify the same staging site’s code. Everyone sees the same live environment, avoiding the “works on my machine” issues from pure local setups.
- Instant Snapshots & Deployment: InstaWP already allows quickly creating throwaway WordPress sites and taking snapshots. With Local Mount, you can spin up a test site in seconds, mount it, modify files as needed, and when done, either share that site or export it. It offers a fluid workflow from development to demo: build locally (on a cloud instance) and deploy or package without leaving your PC interface.
Things to Keep in Mind While Using Local Mount Feature
Using Local Mount is straightforward, but if you encounter issues, consider these tips and caveats:
Ensure the WebClient service is running
The network drive connection uses WebDAV under the hood, which on Windows relies on the WebClient service. This service is enabled by default on most systems.
If mapping the drive fails with an error like “Network name cannot be found” (system error 67) or similar, check that the WebClient service is running on your PC You can do this by typing services.msc in the Run dialog and ensuring WebClient is started.
Use the provided HTTPS URL
Always use the exact Server Address from InstaWP. It will be an HTTPS URL. Windows may refuse to connect if you try to use an insecure HTTP address with basic authentication. The secure HTTPS address ensures encrypted transfer of your data. If you copied the link directly, this shouldn’t be an issue.
Site must be active
Make sure your InstaWP site is running (not expired or stopped). If the site is stopped or has been deleted, the network drive won’t connect, or you might get a generic “network error” during use. If you have a temporary InstaWP site that expired, you may need to relaunch it or extend its time in InstaWP before the mount works.
Credential errors
If you get “Access Denied” errors when trying to open the drive, it usually means a credential issue. Double-check the username/password. Remember that if you toggled the feature off and on again, the credentials may have changed. Always use the current values shown in InstaWP’s Local Mount panel.
Add to Trusted Sites if prompted
In some cases, Windows might require the site to be added to your trusted sites (especially if using certain authentication or older Windows versions). If you see a message like “Before opening files in this location, you must first add the web site to your trusted sites list…”, go to Internet Options > Security > Trusted Sites in Windows.
Add the InstaWP site URL to the trusted list, then try connecting again. This will tell Windows it’s okay to allow stored credentials for that secure site.
Performance considerations
When you edit files over a network drive (WebDAV), there might be slight latency. Small edits will feel instant, but large file operations could be slower than pure local development. If you plan to transfer very large files or many files at once, be patient as it syncs over the internet. Ensure you have a stable internet connection while working to avoid disconnects.
Disconnecting the drive
If you no longer need the mounted drive, you can disconnect it. In File Explorer, right-click the mapped drive (e.g. Z:) and choose Disconnect. This removes the drive from your PC (you can always remap it later). It’s a good idea to disconnect when you’re done to reduce any security risk of leaving a connection open.
Security Considerations and Best Practices While Using Local Mount
When using Local Mount on Windows, you are essentially opening a door from your PC into your WordPress site’s file system. Keep these security best practices in mind:
Secure connection
InstaWP’s Local Mount uses HTTPS for the connection, meaning the data transferred between your PC and the cloud site is encrypted in transit. (Windows actually enforces using HTTPS for WebDAV with login; it will block basic authentication over plain HTTP for security. Always stick to the provided secure URL.
Protect credentials
Treat the mount credentials (username & password) as sensitive information. Do not share them or expose them in version control or scripts. If someone obtains these credentials, they could access and modify your site files. If you suspect the credentials are compromised, disable the Local Mount (toggle off) in the InstaWP dashboard to invalidate them. You can always re-enable it to get a new set if needed.
Use “Remember me” wisely
Only use the “Remember my credentials” option on private, secure computers. When enabled, your Windows Credential Manager will store the InstaWP login. Ensure your PC account is password-protected, and consider not saving credentials on a shared machine. If you did save them and later want to remove access, you can delete the credential entry via Control Panel > Credential Manager.
Disconnect when not in use
For added safety, unmount the drive (and/or toggle off the feature in InstaWP) when you’re done working. This reduces the window of opportunity for any malicious program on your computer to manipulate your site. It also ensures that if your PC is lost or someone logs in, they won’t have ongoing access to your site files.
General Windows security
Keep your system security software up to date. Since the WordPress site’s files are now accessible on your PC, any malware or virus on your machine could theoretically alter those files. Use antivirus protection and avoid downloading untrusted software while your site is mounted. This is similar to standard WordPress security, but worth noting; your local environment’s security affects your remote site when the two are connected.
By following the above steps and precautions, you can safely and efficiently edit your InstaWP site’s files from your Windows computer.
Final Say
InstaWP’s Local Mount feature provides a streamlined development experience by blending the speed of local file editing with the ease of cloud-based WordPress environments. Developers and agencies can rapidly spin up test sites, work on them from their desktops as if the sites were local, and enjoy the best of both worlds; all while avoiding the hassle of local server setup or constant file uploads.
This feature is part of InstaWP’s push toward “local-first” development workflows in a cloud context, making WordPress testing and building faster and more flexible than before.
