Same.new review

What is Same.new?

Same.new is a browser-based application builder with a Next.js workflow, direct file editing, and an integrated terminal. It can generate frontend screens and backend API routes, with integrations for code, data, and authentication. That places it among browser full-stack tools rather than only visual page-copying utilities. Reference-led website work remains an understandable starting use case: a concrete layout can be easier to discuss than an entirely abstract description. The important next step is checking whether the generated behavior and project structure match your needs. A recognizable page is useful, but it does not establish that the rest of an application works.

What’s changed in 2026

The current documentation supports a broader full-stack description than older summaries centered only on reproducing websites. It also makes the deployment path clearer: publishing provides preview and persistent URLs, while custom domains involve claiming the deployment in Netlify. These capabilities are available today, though their release dates are unclear. Current pricing still uses fixed token tiers, with code downloads and premium models attached to paid access. If an older explanation refers to a different plan label, use the current pricing page when deciding what your subscription includes.

What it’s like to use

A reference website can help make the initial direction concrete, and it is possible to adapt that starting point and publish a result. The presence of files and a terminal matters once the work needs manual intervention: a developer can investigate the implementation instead of relying only on conversational instructions. We would keep the initial scope narrow and verify each change before moving on. Successful first publication should not be the only checkpoint. Reopen the project, confirm that edits remain available, and keep an independent copy through the available code workflow before treating the workspace as the only home of important work.

Where it falls short

The most concerning experience pattern is work disappearing or reverting, including changes made manually. Persistent errors and crashes can also turn paid iteration into a sequence with little durable progress. The available experience is limited, so these concerns should guide precautions rather than become a claim that every project has the same outcome. Native mobile apps are outside the documented scope. Deployment ownership is another boundary: claiming a project in Netlify moves resource responsibility to that account. Before committing a long-lived application, check how you will preserve source, reopen it, manage its domain, and maintain any connected database or authentication service.

Pricing and credits in practice

Free includes 500,000 tokens per month. Basic costs $10 monthly with 2M tokens, Pro costs $25 with 5M, Max costs $50 with 10M, and Ultra costs $100 with 20M. Paid tiers include premium model access, downloads, and remixing. Beyond Ultra, the documented extra allowance is $10 for 2M tokens. Check Same.new’s pricing page for annual billing options. These quantities describe model capacity, not a guaranteed number of finished pages or repairs. Keep hosting separate from generation costs: a claimed deployment consumes your own Netlify resources. The practical budget should include time and allowance for confirming that changes remain usable after the first successful preview.

Who should use it (and who shouldn’t)

We would consider Same.new for a bounded web prototype when a reference design and access to editable files are central to the task. It is more suitable for someone willing to check the code and preserve copies than for someone expecting dependable long-term maintenance through prompts alone. A project with strict continuity or spending requirements deserves particular care. Bolt offers a similar browser development category with managed services, while v0 is worth comparing for Next.js work. Replit provides a broader cloud workspace. For native mobile delivery, start with a dedicated mobile option rather than assuming a web project can become one automatically.

Bottom line

Same.new has a clearer technical scope than a simple website-cloning label suggests. Full-stack Next.js support, direct editing, and publishing provide a useful foundation for experimentation. The reason for caution is the durability of progress: a good-looking result or successful deployment does not eliminate the need to verify editing access and preserve the project. We would use it with a narrow goal, deliberate checkpoints, and an independent route to the code. If those habits fit your workflow, it can be worth exploring; if uninterrupted reliability is the main requirement, compare the alternatives before making it the center of a larger application.