SuperCloner for Go High Level: Features & Use Cases | GHLCRM.US

SuperCloner for GoHighLevel is an independent Chrome extension designed to copy HighLevel-built funnel and website pages into another HighLevel builder environment, helping agencies reuse page structures without manually rebuilding every section.

Its current workflow is essentially:

Find a HighLevel Page or Funnel

↓

Copy Funnel Data

↓

Open Destination HighLevel Builder

↓

Paste Funnel Data

↓

Customize

↓

Reconnect Client-Specific Assets

↓

Test

↓

Publish

The tool now supports both single-page cloning and, on eligible SuperCloner plans, whole-funnel cloning. Its current product page says whole-funnel mode can capture all pages in a funnel while preserving page order and editable HighLevel builder content.

SuperCloner should not, however, be confused with HighLevel's native Snapshot system. Snapshots are designed for broader reusable account configuration—including supported workflows, funnels, calendars, forms, dashboards, AI assets, and other configuration—while SuperCloner is primarily useful when the problem is quickly reproducing HighLevel page or funnel design.

For agencies building repeatable client systems beyond page design, see our GoHighLevel for Agencies guide.

Start Your GoHighLevel 30-Day Free Trial →

SuperCloner is a third-party tool built specifically around HighLevel page and funnel cloning.

It is not an official HighLevel product.

The current SuperCloner site identifies the product as part of the All Things GHL ecosystem and explicitly states that it is independent from and not endorsed by HighLevel.

The Chrome Web Store currently describes its purpose as quickly cloning HighLevel funnel or website pages.

Its value proposition is simple:

Existing HighLevel Design

↓

Capture

↓

Transfer

↓

Editable HighLevel Version

Instead of:

Screenshot Existing Design

↓

Manually Rebuild Section

↓

Rebuild Columns

↓

Match Spacing

↓

Recreate Buttons

↓

Match Typography

↓

Recreate Mobile Layout

↓

Repeat for Every Page

For agencies that build many client funnels, eliminating that repetitive reconstruction can be useful.

This distinction is important because older SuperCloner reviews may describe a different product and pricing model.

The current product supports:

Single-Page Cloning

and:

Whole-Funnel Cloning

on eligible plans.

Its current pricing is also credit-pack based rather than the older monthly subscription structure found in some historical reviews.

Therefore, when evaluating SuperCloner in 2026, use current product information rather than assuming older pricing or functionality remains accurate.

According to its current product documentation, SuperCloner is designed to preserve many of the elements that define a HighLevel page.

The current feature list includes items such as:

Page Structure

Sections

Rows

Buttons

Forms

Image Blocks

Video Embeds

Countdown Timers

Testimonials

Pricing Tables

Sticky Bars

Popups

Custom CSS

Tracking Code

Font Settings

Color Schemes

Mobile Breakpoints

SEO Tags

Background Settings

and:

Spacing & Padding.

This makes it substantially different from copying only visible HTML or taking a screenshot.

The objective is to place the recreated design into the HighLevel environment so it can continue to be edited.

The current process is relatively straightforward.

SuperCloner operates as a Chrome extension.

The Chrome Web Store currently lists it as a developer tool for cloning HighLevel funnel and website pages.

Navigate to the HighLevel page or funnel you are authorized to use or have a legitimate reason to reproduce.

SuperCloner detects supported HighLevel pages.

Open SuperCloner and use:

Copy Funnel Data

With whole-funnel mode disabled:

Current Page

→ copied.

With whole-funnel mode enabled:

Entire Supported Funnel

→ captured as a sequence.

Create or open the appropriate destination funnel.

Then open the target builder environment.

Use:

Paste Funnel Data

The copied page or funnel is recreated in the destination HighLevel environment.

Replace:

Brand

Copy

Images

Offers

Forms

Tracking

Business Information

and any client-specific elements.

Do not publish immediately.

Test the resulting assets first.

Single-page mode is useful when you need only one page.

For example:

Existing Landing Page

↓

Copy

↓

New Funnel

↓

Paste

↓

Customize

The current SuperCloner pricing model charges one credit for a single page in page mode.

This can make sense when you want:

One Landing Page

One Sales Page

One Thank-You Page

or:

One Template

without transferring an entire funnel.

Whole-funnel mode changes the economics for larger builds.

Instead of:

Page 1 → Copy

Page 2 → Copy

Page 3 → Copy

Page 4 → Copy

the process becomes:

Funnel

↓

Capture All Pages

↓

Paste Funnel

According to SuperCloner's current pricing model, whole-funnel mode is available on its Growth and Pro options.

The current credit structure is:

SuperCloner currently states that even funnels larger than 50 pages remain capped at 15 credits under this pricing structure.

That can make whole-funnel mode substantially more economical than copying large funnels page by page.

As of the current product offering, SuperCloner advertises four credit packages.

The current product also states that credits do not expire and that there is no recurring subscription requirement for these credit packs.

This is important because older SuperCloner content may reference monthly subscription pricing that no longer matches the current offer.

Always verify current pricing before purchasing because third-party product pricing can change.

In single-page mode:

1 Page

=

1 Credit

In whole-funnel mode:

≤20 Pages

=

5 Credits

21–50 Pages

=

10 Credits

51+ Pages

=

15 Credits.

This means an agency should choose the cloning method based on what it actually needs.

For example:

If you need:

1 page

use page mode.

If you need:

12-page funnel

whole-funnel mode may be more efficient.

If you need:

60-page funnel

whole-funnel mode becomes considerably more attractive under the current credit model.

SuperCloner currently states that failed clones are eligible for credit refunds.

Its current FAQ says users can contact the provider if a clone does not paste correctly and have the applicable credit returned.

This is a SuperCloner policy rather than a HighLevel policy.

Agencies should therefore direct SuperCloner-specific billing or cloning problems to the SuperCloner provider rather than HighLevel support.

Before purchasing an external tool, determine whether HighLevel already handles the specific cloning task.

For simple duplication inside your existing HighLevel environment, native functionality may be enough.

The third-party tool becomes more interesting when the problem is:

Existing HighLevel Page/Funnel

↓

Different Funnel or Account Context

↓

Fast Design Reproduction

The correct tool depends on what is being transferred.

This is the most important comparison.

These tools solve different problems.

Think:

Page/Funnel Design Transfer

Think:

Reusable Account Configuration

HighLevel currently describes Snapshots as reusable templates created from a source sub-account. They can capture selected configuration assets and deploy them into new or existing sub-accounts.

The native HighLevel process is:

Build Source Sub-Account

↓

Create Snapshot

↓

Choose Assets

↓

Load Snapshot

↓

Destination Sub-Account

This can include substantially more than page design.

HighLevel's current Snapshot system supports reusable configuration across categories such as:

Workflows

Funnels

Calendars

Forms

Dashboards

and many additional supported assets.

Recent HighLevel Snapshot functionality also supports advanced assets such as Agent Studio agents and Managed Agents, provided their required supporting assets are selected appropriately.

Use SuperCloner when your problem looks like:

“I need this HighLevel page/funnel structure inside another HighLevel builder quickly.”

It may be useful for:

Landing Page Reuse

Funnel Design Migration

Template Development

Client Funnel Rebuilds

Cross-Account Page Work

Rapid Prototyping

and:

Design Research

provided you have appropriate rights to the material involved.

Use HighLevel Snapshots when the problem looks like:

“I need to deploy a reusable HighLevel business system.”

For example:

Pipeline

Forms

Calendars

Workflows

Funnels

Custom Fields

AI Configuration

↓

Client Sub-Account

Snapshots are therefore particularly useful for standardized agency onboarding.

Suppose your agency has a complete roofing setup containing:

Lead Funnel

Inspection Calendar

Roofing Pipeline

Custom Fields

Appointment Workflow

Missed-Call Workflow

Review Workflow

AI Agent

and:

Internal Notifications

SuperCloner may help with the funnel/page layer.

But HighLevel Snapshots are the native architecture for packaging supported reusable configuration across the broader account.

Therefore:

SuperCloner

≠

Full HighLevel Account Template

That distinction prevents unrealistic expectations.

This is one of the clearest use cases.

Suppose your agency previously created:

Lead Magnet Page

↓

Booking Page

↓

Confirmation Page

and now wants to reuse the design.

Instead of rebuilding:

Sections

Typography

Spacing

Buttons

Mobile Layout

and:

Custom CSS

you can clone the authorized source and customize the resulting version.

This can turn an existing design into a faster starting point.

Agencies sometimes need to reproduce page assets in another HighLevel environment.

The process could be:

Authorized Client Page

↓

SuperCloner

↓

Destination HighLevel Environment

↓

Reconnect Client-Specific Elements

↓

QA

↓

Publish

This can reduce design reconstruction.

However, it does not eliminate migration planning.

You still need to verify:

Domains

Forms

Calendars

Tracking

Automation

Integrations

and:

Client Data

separately where applicable.

Suppose an agency has a proven layout that it owns.

Instead of starting every client project from:

Blank Canvas

the team can start from:

Existing Framework

↓

Clone

↓

Replace Offer

↓

Replace Brand

↓

Modify Structure

↓

QA

↓

Launch

This can shorten production time.

The important word is:

Framework.

Do not treat cloning as an excuse to publish identical content across unrelated clients.

An agency might create authorized templates for:

Roofers

HVAC Companies

Dentists

Gyms

Real Estate

or:

Marketing Agencies

Then:

Template

↓

Clone

↓

Client Brand

↓

Client Offer

↓

Client Copy

↓

Client Tracking

↓

Client Automation

The layout becomes reusable infrastructure.

The final experience should still be adapted to the client.

SuperCloner currently states that it can detect supported HighLevel pages even when HighLevel is operating behind a white-labeled domain.

That can be useful to agencies operating branded HighLevel environments.

However:

White-Labeled HighLevel

does not mean:

Different underlying page architecture

SuperCloner is looking for supported HighLevel-built pages beneath the surface branding.

Consider a funnel containing:

Opt-In

↓

Sales Page

↓

Order Page

↓

Upsell

↓

Thank-You

Recreating every page manually increases production work.

Whole-funnel cloning can make this type of use case more attractive because the current Growth and Pro plans can copy the complete supported funnel under a flat credit schedule based on funnel size.

The economics become more noticeable for larger funnels.

Imagine:

60 Pages

Using page mode:

60 credits

Under SuperCloner's current whole-funnel pricing:

51+ pages

=

15 credits.

For agencies regularly working with large authorized funnel libraries, this can materially reduce cloning-credit consumption.

An agency could maintain a library such as:

Hero Sections

Lead Funnels

Webinar Funnels

Booking Pages

Application Pages

Sales Pages

Thank-You Pages

Then team members can start from proven internal designs rather than rebuilding basic structures.

The larger operational objective is:

Reusable Design System

rather than:

Random Cloning

An existing funnel can also become a training asset.

A junior builder can:

Clone Authorized Template

↓

Inspect Structure

↓

Study Sections

↓

Study Responsive Behavior

↓

Customize

↓

Compare Result

This can help new team members learn how a functioning HighLevel funnel is assembled.

Suppose the agency owns a funnel architecture that works well but needs a new visual identity.

Use:

Existing Funnel Architecture

↓

Clone

↓

Replace Brand

↓

Replace Typography

↓

Replace Images

↓

Rewrite Copy

↓

Update Offer

↓

Reconnect Forms

↓

Test

This can be faster than rebuilding the structural layer.

SuperCloner's current feature list specifically includes Custom CSS among the elements it captures.

This matters because visual differences between two pages can come from more than HighLevel's drag-and-drop settings.

A page may rely on custom styling for:

Animations

Spacing

Typography

Responsive Behavior

or:

Special Components

Preserving CSS can improve visual fidelity.

But it also creates a QA responsibility.

After cloning, review:

Selectors

Classes

Mobile Rules

External References

Hidden Elements

Animations

and:

Unused Styles

A copied page may contain CSS that was appropriate for the original design but unnecessary for the new client.

Cloning reduces rebuilding.

It does not eliminate code review.

SuperCloner currently lists tracking code among the elements it can capture.

This can be convenient.

It can also create a serious operational mistake.

Imagine copying:

Client A Funnel

↓

Client B Funnel

while leaving:

Client A Analytics

Client A Pixels

or:

Client A Tracking Scripts

inside the destination.

Now Client B traffic may be attributed incorrectly.

Therefore every clone should include:

Tracking Audit

before publication.

Check:

Analytics

Advertising Pixels

Conversion Scripts

Custom JavaScript

UTM Logic

Third-Party Widgets

Embedded Forms

and:

External Domains

Do not assume every copied script should remain.

SuperCloner lists forms among supported page elements.

But an agency should still verify where the resulting form submits and which client process it should use.

The desired architecture is:

Destination Form

↓

Destination Contact

↓

Destination Workflow

↓

Destination Pipeline

not accidentally:

Destination Page

↓

Wrong Client Process

Test every form after cloning.

Check every:

CTA

Navigation Button

Anchor Link

Popup Trigger

Calendar Link

and:

External Link

A cloned visual design can look perfect while sending visitors to the wrong destination.

SuperCloner states that mobile breakpoints are among the design information it captures.

That does not remove the need to test:

Desktop

Tablet

and:

Mobile

The destination environment may have different:

Copy Length

Images

Fonts

Offers

or:

Embedded Components

Any of these can alter the layout.

SuperCloner's current FAQ highlights an important edge case.

If the original page was built primarily as raw HTML inside an HTML block rather than native HighLevel builder elements, the cloned result may remain code rather than becoming individually editable drag-and-drop elements.

Conceptually:

Native HighLevel Elements

→ editable HighLevel elements.

But:

Raw HTML Block

→ raw HTML remains the underlying structure.

A cloning tool cannot automatically reconstruct builder components that never existed in the source.

Do not expect page cloning to move:

Contacts

Conversations

Appointments

Opportunities

or:

Historical CRM Activity

Those are separate concerns.

Even HighLevel's broader native Snapshot system intentionally focuses on reusable configuration rather than live customer records and history.

Agencies do not necessarily need to choose only one approach.

A possible architecture is:

for:

Specific Page/Funnel Design

plus:

for:

CRM Configuration

Workflows

Calendars

Forms

Custom Fields

AI Assets

and other supported reusable configuration.

Then:

Client-Specific Setup

for:

Domains

Credentials

Phone

Email

Payment Provider

Users

and other account-specific resources.

This creates a layered deployment process.

Imagine an agency serving HVAC companies.

Its reusable system contains:

HVAC Landing Funnel

Estimate Calendar

Lead Pipeline

Missed Call Workflow

Appointment Workflow

Review Workflow

Custom Fields

and:

AI Configuration

The agency might use native Snapshots to package the broader system.

If it encounters an authorized funnel design that needs to be reproduced separately, SuperCloner may handle that page layer.

The important principle is:

Use the correct tool for the correct asset.

HighLevel's Snapshot functionality has expanded considerably.

Current documentation shows Snapshots can support advanced assets including:

Agent Studio Agents

Managed Agents

Knowledge Bases when selected appropriately

Custom Objects

and other supported configuration.

Therefore, agencies should not assume an external cloner is necessary for every duplication task.

Check native Snapshot support first.

HighLevel currently lets agencies choose specific assets rather than importing an entire Snapshot indiscriminately.

This means:

Snapshot

does not necessarily equal:

Everything

You can choose:

Needed Assets

↓

Conflict Review

↓

Destination

That makes Snapshots increasingly useful for controlled deployments.

When loading into an existing client account, conflicts matter.

HighLevel's current Snapshot workflow allows agencies to review conflicting assets before applying selected configuration.

This is important because:

Existing Client Account

may already contain:

Workflows

Funnels

AI Agents

or other assets.

Blindly overwriting production assets can create problems.

HighLevel states that changing the original source sub-account does not automatically update every Snapshot deployment.

The Snapshot must be refreshed, and relevant updates can then be pushed to linked sub-accounts where supported.

This reinforces an important principle:

Cloning

is not the same as:

Live Synchronization

That applies to both native and third-party deployment thinking.

After cloning:

Source Funnel Changes

do not imply:

Destination Automatically Changes

Treat the destination as its own production asset.

If the agency modifies the master later, it needs a deliberate update process.

For reusable funnels, consider naming such as:

Lead Funnel v1.0

Lead Funnel v1.1

Lead Funnel v2.0

Document:

Date

Changes

Owner

Test Status

Clients Using Version

This becomes increasingly important as the agency grows.

A scalable onboarding process could look like:

Client Signs

↓

Create Sub-Account

↓

Load Appropriate Snapshot

↓

Add/Clone Required Page Assets

↓

Apply Branding

↓

Connect Domains

↓

Connect Phone/Email

↓

Configure Users

↓

Connect Integrations

↓

QA

↓

Launch

The value comes from reducing repetitive setup without removing human review.

A mature production process might use:

Define:

Offer

Audience

Funnel Goal

Conversion Event

Choose:

Existing Internal Template

or:

Authorized External Reference

Transfer the appropriate page/funnel structure.

Change:

Copy

Brand

Images

Offer

Forms

Tracking

Connect:

CRM

Workflow

Calendar

Pipeline

Tracking

Test:

Desktop

Mobile

Forms

Buttons

Tracking

Automation

Publish only after approval.

Cloning technology introduces an important issue:

Ability to copy something does not automatically create permission to use it.

SuperCloner itself explicitly warns against cloning someone else's funnel exactly and republishing it as your own, noting that this may infringe intellectual property. Its recommendation is to use cloning for legitimate modeling, learning, and authorized reuse rather than unauthorized duplication.

Agencies should take this seriously.

Prefer:

Your Own Funnel

Client-Owned Funnel With Permission

Agency Template

Licensed Template

Authorized Partner Asset

or:

Content You Have Explicit Rights to Reuse

Do not assume:

Publicly Viewable

means:

Free to Republish

Those are different concepts.

A useful distinction is:

Learn From Structure

versus:

Copy Protected Creative Work

For example, you might study:

Hero Placement

CTA Sequence

Section Order

Offer Presentation

and then create original:

Copy

Branding

Images

Examples

Proof

and:

Design Decisions

The objective should be faster production, not passing off another creator's work as your own.

Cloning a page does not automatically create SEO value.

If multiple websites publish substantially duplicated:

Copy

Titles

Descriptions

Headings

and:

Content

there may be little reason for search engines to prefer the new page.

After cloning a structure, create original:

SEO Title

Meta Description

H1

Copy

FAQs

Images

Internal Links

and:

Search Intent Alignment

Think:

Clone Framework

not:

Clone SEO Content

A funnel that works for one company may not work identically for another.

Conversion depends on:

Audience

Traffic Source

Offer

Pricing

Trust

Brand

Market Awareness

and:

Sales Process

Therefore:

Proven Layout

does not guarantee:

Proven Results for Every Client

Use cloning as a production accelerator, not a performance guarantee.

Because SuperCloner operates as a browser extension and interacts with HighLevel page-building workflows, agencies should review its current permissions, privacy terms, and security practices before installing it in production environments.

This is good practice for any third-party browser extension.

Ask:

What permissions does it request?

What information can it access?

Who maintains it?

What does the privacy policy say?

Should it be installed in every employee browser?

Do not give every agency user every tool automatically.

SuperCloner is independent from HighLevel.

That means:

SuperCloner Availability

SuperCloner Pricing

SuperCloner Support

and:

SuperCloner Product Changes

are controlled by its provider rather than HighLevel.

Build operational plans accordingly.

Do not make an entire agency delivery process impossible to operate manually.

It can reduce manual reconstruction of authorized HighLevel pages.

Eligible current plans support copying an entire funnel rather than repeating the process page by page.

Supported native builder elements remain useful as HighLevel content rather than merely becoming screenshots.

The tool currently supports custom CSS and tracking information as part of its cloning scope.

Current SuperCloner pricing states that purchased credits do not expire.

Its current credit-pack model is presented as one-time purchases rather than recurring subscription plans.

It is not an official HighLevel product.

Do not expect it to move live contacts, conversations, appointments, and the entire operational history of a client.

You still need to verify:

Forms

Calendars

Domains

Tracking

Workflows

Integrations

and:

Credentials

If the original was built as raw HTML, SuperCloner cannot magically convert it into native drag-and-drop elements.

Technical ability to copy a page does not automatically give permission to republish it.

Never assume:

Clone Successful

=

Production Ready

Advantages:

Maximum Intentional Control

Opportunity to Simplify

No Third-Party Cloning Dependency

Disadvantages:

Slower

More Repetitive

Higher Labor Requirement

Advantages:

Faster Starting Point

Better Layout Reproduction

Useful for Repeated Builds

Disadvantages:

Third-Party Dependency

Credits

QA Still Required

Potential Unnecessary Legacy Code

IP Considerations

The correct choice depends on project frequency and complexity.

HighLevel's Snapshot functionality is broader for account configuration, while SuperCloner is more narrowly optimized around page and funnel cloning.

Starting from scratch still makes sense when:

Brand Is Completely Different

Funnel Architecture Is New

Existing Page Is Poor

Performance Problems Require Redesign

Accessibility Needs Major Improvement

Code Is Messy

or:

There Is No Legitimate Reusable Source

Cloning a bad page simply produces another bad page faster.

The strongest fit is likely:

HighLevel Agencies

Funnel Builders

HighLevel Freelancers

SaaS Operators

Template Creators

and:

Teams Repeatedly Rebuilding HighLevel Pages

It becomes more valuable as repetitive page-production volume increases.

You may not need SuperCloner if:

You Rarely Build Funnels

You Already Own Well-Organized Snapshots

You Only Need Native Account Duplication

You Build Every Client Experience From Scratch

or:

You Rarely Transfer Page Designs

Do not add tools simply because they exist.

Every tool creates another:

Cost

Training Requirement

Security Consideration

and:

Dependency

Evaluate SuperCloner using:

Hours Saved per Funnel

×

Internal Hourly Cost

×

Funnels per Month

Then subtract:

Tool Cost

QA Time

Customization Time

For example, the question is not:

“Is $200 expensive?”

It is:

“Does 40 credits save more than $200 of production cost in our actual workflow?”

That is the more useful business calculation.

Suppose an agency needs to rebuild authorized funnel structures regularly.

Without cloning:

Research

↓

Manual Layout

↓

CSS

↓

Responsive Adjustments

↓

QA

With cloning:

Clone

↓

Brand

↓

Rewrite

↓

Reconnect

↓

QA

If cloning removes several hours of repetitive work per project, the economics may become favorable quickly.

But measure your own production data rather than relying on vendor time-saving claims.

SuperCloner becomes more valuable when it is part of a system.

For example:

Template Library

↓

SuperCloner / Snapshot

↓

Naming Convention

↓

Brand Customization

↓

Integration Checklist

↓

QA Checklist

↓

Client Approval

↓

Launch

Without process, faster cloning can simply create faster chaos.

Every cloned funnel should pass the same checks.

Review:

Brand

Logo

Copy

Images

Forms

Calendars

Buttons

URLs

Tracking

Custom CSS

Custom JavaScript

Mobile

SEO

Privacy Links

Thank-You Pages

Automation

Pipeline

and:

Conversion Tracking

Do this before publishing.

Do not test only the visual page.

Run:

Visitor

↓

Landing Page

↓

Form

↓

Contact Created

↓

Opportunity

↓

Workflow

↓

Email/SMS

↓

Calendar

↓

Appointment

↓

Confirmation

A visually accurate clone with a broken CRM journey is not a successful deployment.

Use a test contact.

Submit the real form.

Check:

Contact Record

Lead Source

Custom Fields

Tags

Pipeline

Workflow

Notifications

Calendar

and:

Tracking

Then remove test data appropriately.

Instead of searching for designs every time, agencies can build an internal authorized library.

For example:

MASTER — Lead Generation

MASTER — Webinar

MASTER — Appointment

MASTER — SaaS Demo

MASTER — Home Services

Then use cloning and Snapshot tools strategically.

This makes production more predictable.

A good agency system separates:

Reusable Structure

from:

Client-Specific Messaging

Reuse:

Layout Logic

Section Framework

Technical Components

Customize:

Headline

Offer

Proof

Images

FAQs

Benefits

Objections

and:

CTA

This creates efficiency without turning every client into a duplicate.

Use this sequence:

1. Confirm Rights to Source

↓

2. Decide SuperCloner vs Snapshot

↓

3. Clone Appropriate Asset

↓

4. Rename Assets

↓

5. Remove Old Brand

↓

6. Rewrite Content

↓

7. Replace Images

↓

8. Audit CSS

↓

9. Audit Tracking

↓

10. Connect Correct Forms

↓

11. Connect Calendars

↓

12. Connect Workflows

↓

13. Test Desktop

↓

14. Test Mobile

↓

15. Test Lead Journey

↓

16. Client Review

↓

17. Publish

This protects quality while retaining the speed advantage.

Explore GoHighLevel With a 30-Day Free Trial →

SuperCloner is an independent Chrome extension designed to copy supported HighLevel funnel and website pages into another HighLevel builder environment. Its current version supports individual-page and whole-funnel cloning.

No. SuperCloner explicitly states that it is an independent All Things GHL product and is not made by, endorsed by, or affiliated with HighLevel.

The current SuperCloner and All Things GHL materials identify Fer Patel as the builder behind the product and the wider All Things GHL tool ecosystem.

Yes. The current Growth and Pro SuperCloner packages include whole-funnel cloning. The tool can capture the pages in a supported funnel and recreate them in the destination HighLevel builder.

Yes. Single-page mode is available across the current credit packages and uses one credit per page.

Current published packages are $20 for 3 credits, $100 for 12 credits, $200 for 40 credits, and $300 for 75 credits. Whole-funnel cloning is currently available with Growth and Pro.

The current SuperCloner offer states that purchased credits do not expire.

Its current public offer is structured as credit purchases without a recurring subscription requirement. Older articles may describe a previous pricing model, so users should verify the current product page before purchasing.

SuperCloner currently charges 5 credits for up to 20 pages, 10 credits for 21–50 pages, and 15 credits for 51 or more pages in whole-funnel mode.

Yes. SuperCloner currently lists custom CSS among the elements captured during cloning.

SuperCloner currently lists tracking code as part of its cloning scope. Agencies should audit copied tracking carefully so analytics or advertising scripts from the source are not unintentionally used for another client.

The current SuperCloner FAQ says it can detect supported HighLevel pages underneath white-labeled domains.

Not necessarily. If the original design was built inside a raw HTML block, SuperCloner explains that the resulting clone can remain HTML because native builder elements did not exist in the source.

No. SuperCloner is primarily focused on page and funnel cloning. HighLevel Snapshots are designed to package broader reusable account configuration, including supported workflows, funnels, forms, calendars, dashboards, AI assets, and other configuration.

No. HighLevel states that Snapshots are designed for reusable configuration rather than contacts, conversations, appointments, and live account history.

Yes. HighLevel currently allows agencies to load selected Snapshot assets into existing sub-accounts and review conflicts before applying them.

Yes. Current HighLevel documentation supports Agent Studio agents and Managed Agents as Snapshot assets, including supported configuration and dependencies when the required assets are selected.

Use SuperCloner when the main task is reproducing an authorized HighLevel page or funnel design. Use Snapshots when the task involves deploying broader reusable HighLevel account configuration. In some agency workflows, both can be complementary.

Technical accessibility does not automatically provide legal or ethical permission to republish another creator's work. SuperCloner itself warns that copying someone else's funnel exactly and publishing it as your own may infringe intellectual property.

No. Conversion performance depends on factors such as audience, traffic, offer, pricing, copy, trust, brand, and sales process. A cloned layout should be treated as a production starting point rather than a guaranteed performance outcome.

No. Audit branding, content, forms, calendars, links, custom CSS, tracking scripts, mobile responsiveness, automation, integrations, and the complete customer journey before publication.

SuperCloner for GoHighLevel is best understood as a production accelerator for HighLevel page and funnel design—not as a replacement for the entire HighLevel deployment system.

Its strongest workflow is:

Authorized HighLevel Funnel

↓

Clone

↓

Customize

↓

Reconnect

↓

QA

↓

Publish

The current SuperCloner product supports:

Single-Page Cloning

and, on eligible plans:

Whole-Funnel Cloning.

Its current credit packages are:

$20 → 3 credits

$100 → 12 credits

$200 → 40 credits

$300 → 75 credits.

Whole-funnel mode currently uses:

Up to 20 pages → 5 credits

21–50 pages → 10 credits

51+ pages → 15 credits.

For agencies repeatedly producing HighLevel funnels, that can remove substantial repetitive page-building work.

But the correct architecture matters.

Use:

SuperCloner

for:

Page/Funnel Reproduction

Use:

HighLevel Snapshots

for:

Reusable Account Configuration

Use:

Client-Specific Setup

for:

Domains

Phone

Email

Credentials

Users

Payments

and other unique operational requirements.

HighLevel's native Snapshot system is increasingly capable. It currently supports selective asset deployment, conflict checking, reusable funnels and workflows, Custom Objects, Agent Studio assets, Managed Agents, and other supported configuration.

That means the strongest agency workflow is not necessarily:

SuperCloner instead of Snapshots

but often:

SuperCloner where page cloning saves time

Snapshots where configuration reuse makes sense

Human QA before launch

Most importantly, cloning should be used responsibly.

Prefer:

Your Own Assets

Client-Owned Assets

Licensed Templates

and:

Material You Have Permission to Reuse

The technical ability to reproduce a publicly accessible page does not grant ownership of another creator's design, copy, images, or intellectual property. SuperCloner itself makes this distinction in its current guidance.

For agencies, the real value is therefore not:

“Copy everything.”

It is:

Build Once

↓

Reuse Legitimately

↓

Customize Intelligently

↓

Test Carefully

↓

Deploy Faster

That is where SuperCloner can fit into a scalable HighLevel agency production system.

Start Your GoHighLevel 30-Day Free Trial →