Local Connect

The Local Connect feature helps you move a site between Local and your remote hosting provider.

By pulling a site down to Local, you can quickly create a sandbox for experimenting with new ideas or testing updates to plugins and themes. Once you’re finished working on the site, deploying is easy by clicking the “push” button!

Throughout the development process, you can pull down changes made to the remote site so you always have the latest content. Along the way, you can push works-in-progress to a staging environment to get feedback from co-workers or clients.

Getting started with Local Connect is easy:

  1. Connect Local to your hosting provider (Flywheel or WP Engine).
  2. Connect a specific local site to a remote site.
  3. Start pushing or pulling and select the remote environment you’d like to use!

Connecting to a hosting provider

See the specific instructions for Connecting to Flywheel or Connecting to WP Engine. If you’d like to see Connect support additional hosting providers, vote on those Feature Requests in the Forums.

Pulling and Pushing

After linking Local to your hosting provider, pull a site down by navigating to the “Connect” tab in Local.

For sites you already have in Local, select the host you want to work with from the Site Overview page. You can click the “Pull” button to download changes from the remote site, or click the “Push” button to deploy your Local site to staging or production.

A screenshot of the Connect tab in Local where you can pull a remote site down.
On the “Connect” tab, click the “Pull to Local” button to import a remote site into Local.
A screenshot of the site overview page showing how to link a site to a remote host.
Link a local site to a remote host by clicking the “No host selected” link in the lower-right corner of the site-overview page.
A screenshot of the push button on the site overview page.
Deploy a site by clicking the “Push to…” button in the lower-right corner of the site-overview page in Local.

Remote environments

Depending on the hosting provider, you have options for the kind of environment you can push-to or pull-from:

By default, the production environment is used, but if you’d like to deploy to a staging environment that doesn’t exist, Local will direct you to create that environment.

A screenshot of selecting the remote environment to work with.
When pulling or pushing a site, select the remote environment you’d like to work with.
A screenshot showing Local prompting to enable staging on a remote environment.
If a staging environment doesn’t exist remotely, Local will prompt you to create one.

MagicSync

The MagicSync viewer allows you to quickly see which files have changed between the Local and remote site and select which of those files should be deployed. More details about using the MagicSync viewer can be found in this help doc.

If you don’t need this fine-grained control over what gets deployed, you can disable MagicSync from “Preferences > MagicSync”.

A screenshot showing the MagicSync setting in Local's preferences.
Enable or disable MagicSync setting in Local’s preferences.

Path Exclusions for Local Connect

When pushing or pulling a site, Local excludes certain files for security, performance, or reliability reasons.

Local excludes these paths relative to your site’s root:

Local excludes every occurrence of these paths within your site:

Special exclusions based on regex patterns: