GoHighLevel Snapshots Tutorial: Create, Share and Load (2026)

If you build the same GoHighLevel setup for every client, snapshots are how you do it once and copy it everywhere.

A GoHighLevel snapshot is a reusable pack of sub-account setup, pipelines, calendars, forms, workflows and more, that you can create, refresh, share and load into other accounts. It copies the build, not your contacts.

Snapshots have had a load of updates this year: version history, load history, better share links and asset protection. This guide walks the full flow from the Faceless GHL tutorial, with a bit more detail on each screen 👇

TL;DR: GoHighLevel snapshots

• What they are: reusable setup packs for sub accounts, not a dump of client data.
• Where they live: agency view → Sub accounts → Account Snapshot.
• Create smart: pick only the assets you want. You do not have to take everything.
• Refresh: new versions pull dependent tags and custom values so loads do not break.
• Load carefully: watch the conflicts screen. An overwrite cannot be undone.
• Skip the blank page: niche packs live in our Watch the free masterclass.

If you only remember one thing: refresh before you push, and never tick an overwrite you are not sure about.

What a GoHighLevel snapshot is

A snapshot is a saved copy of the setup inside a sub account. Think pipelines, calendars, forms, workflows, funnels, templates and the tags or custom values those pieces need.

It is the agency answer to rebuilding the same plumbing offer, med spa funnel or HVAC pipeline for the tenth time. Build it once in a clean sub account, save the snapshot, then load it into the next client.

If you are brand new to the platform, start with What Is GoHighLevel for the definition, then the Explained tour for a live menu walkthrough. Snapshots sit on top of that once you have something worth cloning.

Who snapshots are for

Agencies

This is the main job. One starter pack per niche, then load it into each new client sub account. Share links and marketplace options also let you distribute packs to other agencies.

Operators with several locations

If you run more than one location or brand inside HighLevel, snapshots keep calendars, pipelines and forms consistent without hand-building each one.

People buying a head start

Turn this into a system you can sell. Watch the free masterclass for the agency method, or get free access to the community through Greg's GoHighLevel link.

Watch: GoHighLevel snapshots tutorial (2026)

Prefer to watch first? The full create → refresh → share → load walkthrough is below. It is under five minutes on the current snapshot UI.

• 0:00 GoHighLevel snapshots: build once, copy everywhere
• 0:17 What changed with snapshots this year
• 0:41 Where snapshots live
• 0:58 Create a snapshot and pick only the assets you want
• 1:24 Version one and the snapshot details
• 1:37 Refresh to version two (32 added, not 8)
• 1:59 Share links and asset protection
• 2:23 Load updates to sub accounts
• 2:47 Load a snapshot into a sub account
• 3:16 Tips: load history, refresh first, overwrites
• 3:47 More GoHighLevel updates

What changed with snapshots this year

Snapshots are not new, but the tooling around them is. In the video I call out three big upgrades you will feel day to day:

• Version history on each snapshot, with a clear record of what each refresh added.
• Load history on each sub account, so you can see which snapshot was loaded, when, who did it and which version.
• Share and protect options, including permanent, one-time, email, account-specific and marketplace links, plus asset protection.

HighLevel has also expanded what can ride inside a snapshot through 2025 and 2026, including better asset selection, push retries, AI Studio projects and Smart Lists support. The steps below stick to what the tutorial shows on screen.

Practically, that means older YouTube videos can still teach the idea of snapshots while missing the version history panel, the conflicts wording, or the load history under Snapshot actions. If a tutorial is older than late 2025, treat the menu labels as approximate and match the clicks to your current agency Account Snapshot screen.

Where snapshots live

Open your main agency account, not a sub account. Go to Sub accounts, then Account Snapshot. That list is the home for every pack you own.

Across the top you get four tabs:

From here you create, refresh, share, push updates and open history. If a screen looks empty, check you are in the agency view, not inside a client sub account.

The list columns typically show the snapshot name, how many sub accounts use it, the current version, created date and last updated date. Row actions include create new account from the pack, refresh, load updates, and a three-dot menu for settings, copy ID, share, sell on marketplace, view history and delete.

Create a snapshot and pick only the assets you want

Click Create new snapshot. Give it a clear name. In the video I use Northline Plumbing Starter, then pick the demo plumbing sub account as the source. Click Next.

This is the bit most people skip. HighLevel lists every asset in that sub account: calendars, pipelines, workflows, forms and more. You do not have to take the lot.

For a starter kit I only tick pipelines, calendars and forms. Then click Create. It only takes a few seconds.

Name the pack like a product, not like a dump. “Northline Plumbing Starter” tells a teammate what it is for. “Final copy 3” does not. When you sell or share packs later, clear names also stop you loading the wrong version into a live client.

Version one and the snapshot details

After create, the pack sits on version one. Click the name to open snapshot details.

The Assets tab shows exactly what is inside. Version history lists every version with what was added. Right after create you will only see the one version.

That details view is your source of truth before you share or load anything. If the Assets tab does not match the starter kit you meant to ship, refresh and fix it before the pack goes into a live client account.

Refresh to version two (and why the count jumps)

Say you changed something in the source sub account, or you want to add more assets. Click the refresh icon on the snapshot row. You get the same asset list again.

In the tutorial I also tick the workflows, then click Refresh. The pack moves to version two.

Look at version history carefully. It reported thirty two added, not eight. That is because HighLevel also pulled in the tags and custom values those workflows use. That dependency pull is what stops the load from breaking later.

Once a pack has several workflows, it also helps to see how those automations connect. That is what Workflow Maps is for inside a sub account.

Share links and asset protection

Click the three dots on the snapshot, then Share snapshot.

In the link-type dropdown you can choose:

• Permanent link, stays usable until you revoke it.
• One time link, burns after a single use.
• Email link, tied to an email invite path.
• Account-specific links, only work for one specific account.
• Marketplace link, for selling the pack.

Underneath, turn on Enable assets protection if you want recipients to use the snapshot in their own accounts without being able to share it on or resell it. Then click Get link and send it.

Protection will not replace a clear licence in your own store terms, but it is the product-side control you should know about before you hand a pack to another agency.

Load updates to sub accounts

If a snapshot is already loaded into some accounts, the upload icon is Load updates to sub accounts.

You get tabs for All, Linked and Available. Linked shows every account already using the pack, so you can push changes to all of them in one go.

In the video nothing is linked yet because the new Northline pack had not been loaded anywhere. One hard rule: you cannot load a snapshot back into the account you made it from. That is why I cancel the modal and switch to a normal first load with an HVAC snapshot instead.

Load a snapshot into a sub account

Here is the first-load path shown in the tutorial:

1. Go to Sub accounts and open the destination with Manage Client.
2. Click Actions → Snapshot actions → Load snapshot.
3. Pick the snapshot (in the video, an HVAC pack) and click Proceed.
4. Choose assets. I click Skip at the top to untick everything, then select only the pipelines.
5. Review the conflicts screen. Anything you tick gets overwritten.
6. With no conflicts, click Proceed, type confirm, then Proceed again.

HighLevel help describes the same sequence for loading into an existing sub account: pick the snapshot, select assets, resolve override vs skip on conflicts, type confirm, then wait for the email when it finishes.

Load vs push is the other language trap. Load is the first deploy into an account. Push / load updates is for accounts that already have that snapshot linked. Mixing them up is how people try to “update” an account that was never linked, or wonder why the upload icon has nothing under Linked.

Tips so you do not get caught out

Most snapshot mistakes are boring, not mysterious. People select every asset on create, skip the conflicts screen on load, or push without refreshing. The tips below are the ones that stop those three from wrecking a live client sub account.

• 👉 Use load history. Under Actions → Snapshot actions you now get View snapshot history. It shows which snapshot was loaded, when, who did it and which version.
• 👉 Refresh before you push updates. Otherwise you push the old version to every linked account.
• 👉 Treat overwrites as permanent. If you are not sure, leave the conflict unticked.
• 👉 Snapshots do not copy contacts. They copy the setup. That is exactly what you want when cloning a build.
• 👉 Keep source accounts clean. Build the pack in a demo or template sub account, then load outward. Do not try to load the pack back into its source.

Turn this into a system you can sell. Watch the free masterclass for the agency method, or get free access to the community through Greg's GoHighLevel link.

Can agencies sell snapshots?

Yes. From the snapshot menu you can open share options that include a marketplace link, and there is a Sell on marketplace path in the product. Asset protection helps stop a buyer from resharing or reselling your pack.

Turn this into a system you can sell. Watch the free masterclass for the agency method, or get free access to the community through Greg's GoHighLevel link.

Whether you sell inside HighLevel's marketplace or outside it, the same product rules apply: refresh before you push, protect assets when you share, and never overwrite a live client asset unless you mean to.

If you are packaging for your own store, keep a private source sub account as the gold master. Refresh the snapshot from that master, test-load into a throwaway sub account, then push or share. That dry run catches missing tags and custom values before a paying client sees them.

Snapshots pros and cons

FAQs: GoHighLevel snapshots

Verdict: what to do next

Snapshots are how HighLevel agencies stop rebuilding the same account by hand. Create a skinny starter pack, refresh when the source improves, share with protection when needed, and load with your eyes on the conflicts screen.

• ✔️ Create from a clean template sub account
• ✔️ Pick only the assets you need on day one
• ✔️ Refresh before every push to linked accounts
• ✔️ Leave unsure overwrites unticked
• ✔️ Or skip the blank page and start from the Watch the free masterclass

Prefer free courses while you learn the menus? Open the Get free access.

New to the platform itself? Read What Is GoHighLevel first, then come back here once you have a sub account worth cloning. Snapshots assume you already know where CRM, Sites and Automations live.

Related posts

Information and education only. Nothing here is a promise or guarantee of income; results depend on your own work, skills and situation.