Step 1
1. Capture a clean snapshot
- Paste any public URL you want to explore.
- Kloner creates a visual snapshot of the page for you.
- You can keep multiple snapshots for the same project and label them however you like.
Demo
Kloner · Product Guide
Documentation
Kloner lets you capture a website, turn it into an editable preview, and ship a polished version as your own project. This page explains the core features, how credits work, and what the different plans unlock.
Website captureEditable previewsLaunch-ready outputFair-use credits
Core workflow
From someone else’s site to your own version
Kloner is built around a simple, guided flow: capture, preview, edit, and publish. Each step is designed to be visual, safe, and repeatable.
Step 2
2. Generate an editable preview
- Pick any snapshot and tell Kloner to create a preview.
- The preview looks like the original but is now editable inside your workspace.
- You can revisit and regenerate previews as your ideas evolve.
Demo
Preview created
Step 3
3. Edit visually
- Change copy, swap sections, adjust layouts, and tailor the design to your brand.
- You stay in one focused editor instead of juggling multiple tools.
- Experiment freely: your original snapshot is always preserved as a reference.
Demo
Edit headings, paragraphs, and sections visually. Kloner keeps your working version and your original snapshot separate.
Step 4
4. Export or launch
- Once you’re happy with the preview, export or connect it to your deployment flow.
- Paid plans unlock direct handoff into supported hosting providers for a smoother launch.
- You can revisit, duplicate, and evolve previous versions without losing your work.
Demo
Ready to launch?
Paid plans unlock direct integrations with popular hosting platforms.
Usage limits
How the credit system works
Credits keep usage predictable and fair. They also create natural upgrade points for teams that outgrow the Free tier.
Two things that use credits
- Snapshot actions – every time you ask Kloner to capture a fresh snapshot of a URL, it uses a small number of credits.
- Preview generations – each time you spin up a new editable preview from a snapshot, it uses another small batch of credits.
Typical daily allowances
Free
A handful of snapshots / dayEnough previews to test the product
Pro
Comfortable daily snapshot allowanceGenerous preview allowance for active builders
Agency
High volume for client workHigh volume for project iterations
Enterprise
Tailored to your teamTailored to your workloads
What happens when credits run out
- Snapshot and preview buttons clearly show when you’ve hit your daily limit on the current plan.
- Instead of silently failing, Kloner shows a gentle upgrade prompt that explains what you’d gain by moving up a tier.
- Credits automatically refill on a rolling daily basis, so casual users can keep using the Free plan without friction.
Demo · Credit counters
Current plan·Free
Snapshot actions1/3 left
Preview generations1/5 left
Once a counter reaches zero, Kloner pauses that action for the day and guides you toward either upgrading or trying again tomorrow.
Fairness principle: no credits lost on system errors
If something on our side fails, that attempt doesn’t count against your daily credits. Credits are meant to reflect successful work, not failed attempts.
Monetization
Plan overview
Kloner is usable on Free, and intentionally rewarding on paid tiers. The idea is simple: real value at every level, and extra power as you grow.
Free
Perfect for quick experiments and trying Kloner without commitment.
- Limited daily snapshots and previews
- Core editor experience included
- No payment details required
- Good for solo testing and personal tinkering
Pro
Most popularBuilt for solo founders, freelancers, and small product teams.
- Higher daily allowances
- Priority processing windows
- Access to more advanced editor capabilities
- Support for streamlined launch workflows
Agency
For agencies and studios cloning and customizing sites for clients.
- High-volume usage patterns supported
- Agency-friendly credit allowances
- Features designed for client delivery pipelines
- Flexible options for custom agreements
Enterprise discussions focus on scale, governance, and custom workflows. Reach out through in-app contact options if you need something beyond the standard tiers.
Trust & boundaries
Safety, privacy, and fair use
Kloner is designed to be useful for builders while respecting websites, users, and hosting providers.
How Kloner treats other websites
- Kloner only works with publicly accessible content.
- You are responsible for ensuring that your use respects the original website’s terms, local laws, and any relevant licensing.
- We encourage users to treat Kloner as a starting point for their own original work, not a way to pass off someone else’s site as-is.
Privacy and data handling
- Kloner focuses on page visuals and layout, not on tracking individual visitors or private user data.
- Captured material is kept inside your account and used to power your previews and projects.
- We do not expose internal implementation details or any sensitive infrastructure information in public docs.
Guardrails against abuse
- Daily credits and sensible pacing are built in to discourage automated abuse and scraping behavior.
- Certain advanced actions are locked to paid plans where there is a clearer accountability trail.
- Suspicious or abusive usage patterns can be rate-limited or blocked to protect the platform and other users.
Working with your team
- Pro and Agency tiers are designed for collaborative workflows while still keeping one clear account owner.
- Teams can standardize on Kloner for consistent previews and faster client sign-offs.
- If your use case is unusual or high-risk, talk to us before scaling up, so we can help design an appropriate setup.
Library
Export options and practical guides
These sections stay high-level and are written for both technical and non-technical users. They describe responsibilities and tradeoffs without exposing internal systems.
Routing guides
- Explains how exported projects can be organised into simple, predictable routes.
- Covers common patterns such as home pages, landing pages, and basic sub-pages.
- You decide how to wire these routes into your own framework or hosting provider.
SEO templates
- Outlines safe defaults for titles, descriptions, and basic on-page structure.
- Focuses on clarity and relevance, not on exploiting search engines.
- You remain responsible for any SEO strategy, claims, and compliance.
Font subsetting
- Describes why trimming unused font weights and character sets improves load time.
- Avoids bundling full font families when only a few styles are needed.
- You are responsible for licensing any fonts you choose to use in exports.
Image optimization
- Explains basic sizing, compression, and responsive image ideas in plain language.
- Encourages you to keep file sizes reasonable without damaging clarity.
- You choose where images are hosted and remain responsible for the assets you upload.
Deploy checklists
- Provides simple pre-launch checks: links working, copy reviewed, legal pages present.
- Highlights that you must verify any tracking pixels, consent flows, and policies.
- Reminds you to confirm that the project respects all relevant terms and regulations.
Export options
- Summarises the main ways to move from preview to your own hosting environment.
- Keeps the language platform-agnostic so you can choose Vercel, Netlify, or others.
- Clarifies that once exported, you own and control the project code and its use.
First session
A simple way to get value in 10 minutes
If you’re new to Kloner, this is a straightforward flow to run on your first day.
Step 1
Clone something familiar
- Pick a site you already know well.
- Capture a snapshot and generate a preview.
Step 2
Make it yours
- Change the headline to match your product.
- Swap one section to reflect your own offer.
Step 3
Decide if you need more
- If you hit limits but see value, upgrade straight from the prompts.
- If not, let credits reset and keep exploring at your own pace.