How your monthly clone quota works

Overview

Every Clonerix plan has a monthly clone quota. Free tier gets two clones every 30 days. Pro gets fifteen. Max is unlimited. This article explains exactly what counts as a clone, when and how the quota resets, what to do if you run out, and how not to waste your quota on avoidable failures.

If you only read one section, read the one titled "What counts, what does not." It contains the single most commonly misunderstood detail of the billing system.

Key terms

Clone. The act of submitting a URL to the Clonerix engine, running it through the four-stage clone pipeline (Fetch, Analyze, Reconstruct, Prepare), and producing an editable project in your dashboard. One submitted URL equals one clone unit consumed for billing purposes, with specific exceptions for failed clones as described below.

Billing period. The 30-day window during which your quota applies. For new subscriptions, the billing period begins on the day you subscribe. It does not reset on the calendar first of the month. Free accounts reset on the 30-day anniversary of account creation.

Reset date. The exact calendar day and time your quota counter rolls back to zero and a fresh billing period begins. You can view your personal reset date at any time from Billing > Usage in the dashboard.

Failed clone. Any clone attempt that does not successfully produce a working editable project. Failures can happen for many reasons, including source-site errors, network issues, platform bugs, or source pages that are behind authentication or access control.

What counts against quota, what does not

Counts as one clone:

• Any successful clone of a single URL that completes all four pipeline phases and lands you in the editor with a working project.
• Any successful multi-page clone where you checked additional subpage boxes during the clone flow. Multi-page clones count as exactly one clone unit regardless of how many subpages you selected during setup. One initiated clone job, one unit consumed.
• Deliberate re-clones of the same URL because you did not like the output of the first attempt. Each submitted clone job counts separately.

Does NOT count against your quota:

• Any clone that fails before completing the Prepare phase and does not produce an editable project. You will see an explicit error message in the UI if this happens. The quota counter is automatically refunded within a few minutes of the failure confirmation.
• Any clone that returns a source-site HTTP error code (404, 500, 403, 429, 503, etc.) from the target origin server.
• Any clone blocked by the Responsible Use enforcement pipeline before reaching the reconstruction phase.
• Republishing existing projects. Publish and Republish actions are unlimited on every plan. They do not consume clone credits.
• Editor saves, version history restores, ZIP exports, preview generations, or any action taken inside an existing project. Clone quota is only consumed when you click the Clone button on a new URL.
• Opening, editing, and otherwise using existing projects in your dashboard. Projects you already created never expire and never incur extra quota charges for continued use.

The single biggest misconception we see in support tickets is users thinking that publishing a project, editing it, or adding additional subpages later consumes another clone. It never does. Clone quota is consumed once per new URL clone job.

How to check your current usage

From the dashboard, click the account menu in the top-right corner and select Billing. On the Billing page, navigate to the Usage tab.

The Usage page shows three numbers prominently at the top: clone units consumed this billing period, your total plan quota for the period, and the number of days remaining until your counter resets.

Below the summary is a detailed per-clone activity log. Each row shows the timestamp of the clone attempt, the source URL that was submitted, whether the clone succeeded or failed, whether it counted against quota, and a link to open the resulting project if one exists.

If you believe a specific clone entry was incorrectly counted against your quota when it should not have been, click the three-dot action menu on that row and select Dispute quota charge. Billing reviews disputes manually within two business days. Approved disputes result in a quota credit applied to your current billing period.

Reset behavior

Your clone counter resets automatically at 00:00 UTC on the 30-day anniversary of your subscription start date. No action is required from you. The new billing period begins with a fresh quota at the level of your current active plan.

Quota from one period does not roll over to the next period. It is intentionally use-it-or-lose-it to keep pricing simple and predictable. There is no way to bank unused clone credits for a future month.

If you upgrade mid-cycle, the higher quota is applied immediately and prorated. For example, if you upgrade from Free (2/month) to Pro (15/month) exactly halfway through your billing period, you receive the remaining 15 pro-rated clone credits for the rest of that cycle, plus a full 15 for the next complete cycle when you renew.

What to do if you run out of quota

Running out of quota before the end of your billing period is a good signal that you are ready for the next tier up. Upgrade from Billing > Change plan. The upgrade takes effect immediately and you receive the prorated balance of the higher-tier quota for the remainder of the current period, as described above.

If you occasionally run slightly over quota on a tier that is otherwise correct for your typical usage, wait for the natural reset. Quota resets every 30 days like clockwork. You can continue to edit, publish, republish, and work with existing projects indefinitely while waiting for the reset. Only new clone jobs are blocked.

Short-term promotional quota bumps are occasionally available for existing customers who are actively evaluating an upgrade, running a large one-off client project, or presenting Clonerix at a public workshop or conference. Contact support from the account email with a brief explanation of the situation if this applies to you. We do not guarantee free promotional credits, but we do consider every request.

Avoid wasting quota

Nine times out of ten, users who burn through quota faster than expected are making one or more of these avoidable mistakes. Fixing them usually doubles or triples the effective value of every plan tier.

Verify source URLs before clicking Clone. If the page you want to clone is not publicly accessible (broken link, typo in URL, page moved behind a login since you last saw it), the clone will fail and consume a refunded quota entry but cost you time. Paste the URL into an incognito browser window first to verify it loads for a random stranger on the internet.

Use the multi-page subpage selector on the first pass. When cloning a full site or funnel, check every subpage you need in the initial clone dialog. Subpages discovered and cloned as part of the initial multi-page job do not cost extra quota. Going back later and cloning each subpage URL individually as separate jobs would cost one unit each.

Clone from the canonical production URL. If the site has staging, preview, and dev variants that eventually render with different content, clone the live production URL as your source. Cloning staging first, realizing it differs from production, and then cloning production separately burns two units for no reason.

Do not re-clone just because of minor cosmetic issues. Almost every small problem with a first-pass clone can be fixed in the visual editor in under a minute. Font slightly off? Tweak the design tokens. One image slot rendering incorrectly? Replace it manually. Alignment off in one section? Adjust spacing in the inspector. Re-cloning the same URL because you want to "try again for a better result" almost never fixes issues and always costs another quota unit.

Save intentional research clones for the end of the billing period. If you want to clone a bunch of competitor pages just to build up your personal swipe file for inspiration, batch those research clones near the end of the billing period after all production client work is already done. That way you never burn quota on research clones and then have none left for urgent client projects at the end of the cycle.

Quota behavior during plan changes

Upgrade mid-cycle. You are immediately bumped to the higher plan quota. A prorated calculation runs and you are credited the difference. The clone counter is not reset; the cap simply increases mid-period.

Downgrade mid-cycle. No change to your current billing period quota. You retain access to the higher-tier quota level until the next natural reset date. At that point, the counter resets at the lower tier value. Any projects you created while on the higher tier remain editable.

Cancel plan entirely. At the next natural reset date after cancellation takes effect, your plan reverts permanently to the Free tier with the Free tier quota of two clones per 30-day window. No data is deleted. No projects are removed.

Lapsed Max subscription re-subscribed after a gap. If you had a Max account, canceled for one or more billing periods, and re-subscribed, your billing period anniversary and reset date shift to the date of the new subscription. You do not inherit the reset anniversary from the canceled subscription.

Enterprise and team plan quota

Max plan has unlimited clone quota. Individual seats on a team Max plan each have unlimited quota. There is no team-level aggregate cap and no per-seat hidden throttling in practice.

Very heavy users occasionally trigger internal abuse-detection signals when cloning hundreds of URLs per hour in a scripted or automated fashion. This is a safety feature, not a quota limit. If you have a legitimate use case that requires very high-volume cloning (research datasets, archival work, large-scale competitive intelligence), contact sales in advance. We will adjust the internal thresholds for your account rather than flagging you automatically.

Enterprise custom contracts often include explicit volume guarantees and SLAs around clone throughput. If your usage profile requires tens of thousands of clones per month, talk to the enterprise sales team rather than trying to shoehorn your workload into a standard Max subscription.

Frequently asked questions about quota

If one clone fails and I retry the exact same URL immediately, does the retry count? The first failed clone is automatically refunded. The retry, if it succeeds, counts as one. If it fails again, it is also refunded. Failures never count. Only successful final outputs count.

Can I transfer or gift unused quota to another user? No. Quota is account-specific and non-transferable. It cannot be sold, traded, gifted, or pooled between separate user accounts.

If I create a clone, then delete the project, do I get the quota back? No. Quota is consumed at the time the clone job is successfully completed. Deleting the output project later does not refund the quota unit.

Do ZIP exports count against quota? No. Exports, publishes, republish, version saves, and all post-clone operations on an existing project never count against clone quota.

Do projects expire if I don't touch them? No. Projects remain in your dashboard forever unless you explicitly delete them. You can come back to edit and republish a project you cloned two years ago on an old billing period without any impact on your current quota.

Is there a pay-per-clone option if I don't want a subscription? Not currently. All plans are flat-rate subscriptions with the quota structures described in this article. Pay-per-use clones for very infrequent users are something we have explored and may introduce in the future.

---