From prompt, URL, or screenshot to a published site

CopySite AI is built for a simple commercial outcome: turn an idea, a reference URL, or a screenshot into a site you can actually ship. The product loop is not just "generate a page." It is input, build, preview, recover, deliver, and upgrade when the work becomes valuable.

Start with a real source

You can begin in three ways:

1. Prompt - describe the site, audience, tone, sections, and desired stack.
2. URL - paste a public page you are allowed to rebuild so CopySite can capture structure, hierarchy, and visual cues.
3. Screenshot - upload an image when the source is a design, competitor page, or older site you want to recreate as editable React.

New users receive starter credits and can keep two active CopySite projects on the free plan. That is enough to test the full workflow before choosing a paid plan.

Generate editable code, not a locked mockup

Each project runs inside a sandboxed coding-agent loop. CopySite writes React and Tailwind files, records the run log, and creates an initial snapshot. The workspace then gives you:

• a live preview,
• generated files,
• chat-based refinement,
• build logs,
• source evidence for URL or screenshot projects,
• visual comparison when a screenshot is available.

This matters because the output has to be inspected, changed, and shipped. A static preview is not enough for client work or production launches.

Use snapshots as the recovery system

Every meaningful change creates a snapshot. If a refinement goes in the wrong direction, restore a previous version instead of restarting the project. Use compare views to review what changed before you accept a version.

For teams and agencies, this turns AI generation into an auditable workflow: you can show the source, the generated result, the diff, and the recovery path.

Deliver the result

When the site is ready, choose the delivery path that matches the job:

• Preview the live build for review.
• Export the project bundle for handoff.
• Publish the current snapshot.
• Push to GitHub when the next step is a repo, pull request, or client-owned source handoff.

CopySite also records launch evidence so you can see what passed, what still needs manual action, and what to do next.

When to upgrade

Upgrade when you need more active projects, larger credit allowances, team workflows, repeated exports, or production delivery support. If automatic checkout is not ready in your region or account yet, use the manual upgrade path from pricing, billing, or credits. The support request gives the operator enough context to grant credits or complete the plan change.

The goal is straightforward: start free, prove the workflow on two real projects, then pay when CopySite is helping you ship faster.