Cloud app builder
How to use
Replit.
Planning, building, previewing, and publishing web or mobile applications from a brief while retaining access to the generated project and development environment.
Replit is a AI application builder and cloud development environment. Planning, building, previewing, and publishing web or mobile applications from a brief while retaining access to the generated project and development environment. This guide covers the whole path in one place: official access, a first session that produces something reviewable, the checks that make output trustworthy, and the permissions worth limiting before you connect real work.
AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.
Access & setup
Find, install, and sign in to Replit
Get into the official Replit experience with the right account and a setup you understand.
- 01
Start at https://replit.com/ and confirm the domain before entering account or payment information.
- 02
Availability: Browser-based project editor with mobile access and cloud previews, development, and publishing.
- 03
A Replit account is required. Additional accounts and credentials may be needed for mobile testing, app stores, custom services, or connected integrations.
- 04
Sign in with the account you intend to keep using, then review plan, data, notification, and permission settings.
- 05
Run one low-risk test task before connecting sensitive files, repositories, or workspace data.
- Use official download pages.
- Review permissions during setup.
- Keep installers and applications updated.
First session
Your first useful Replit session
Learn the interaction loop using a small task with a clear outcome.
- 01
Start a new project with one primary user flow, a visual direction, data assumptions, and a strict first-version scope.
- 02
Review Agent’s plan before authorizing the build.
- 03
Test every promised interaction in Preview at desktop and mobile widths.
- 04
Inspect the code, data persistence, secrets, logs, and deployment behavior before publishing.
- State the outcome before the background.
- Provide the real source material.
- Review the result before expanding the task.
Quality control
Check the quality of Replit output
Turn generated code into a change you would put your name on in review.
- 01
Restate the intended behaviour and the acceptance criteria before reading a single generated line.
- 02
Read the diff rather than the chat summary; the summary describes intent, the diff describes what actually changed.
- 03
Run the test suite, then write a test that would fail if the change were wrong, and confirm it passes for the right reason.
- 04
Check the edges the model tends to skip: error paths, null and empty cases, concurrency, and migration or rollback behaviour.
- 05
Trace every new dependency, network call, and file write, and confirm each one is genuinely required.
- Review the diff, never the description of the diff.
- A passing test suite proves the tests pass, not that the change is correct.
- Keep changes small enough that a human can actually review them.
Privacy & permissions
Use Replit safely
Give the tool enough repository access to help, and no more than that.
- 01
Decide what the tool may read and what it may write before connecting a repository.
- 02
Scope tokens and integrations to the narrowest repository, branch, and permission set that still works.
- 03
Keep secrets out of the context window: use environment variables and secret stores, never inline credentials.
- 04
Require review before generated code touches authentication, payments, permissions, migrations, or deletion paths.
- 05
Audit what the integration retained after the session, and revoke access that is no longer needed.
- Generated applications still require engineering and product review. Confirm security, billing, persistence, accessibility, dependencies, and failure behavior before sharing beyond a prototype.
- Follow your organisation's approved-use policy.
- Never treat fluent output as authorization to act.
Core workflows
Step-by-step ways to use Replit for the work it does best.
Each workflow is a separate guide with its own steps and review checkpoints.
Take one product flow from prompt through Plan, Preview, testing, and a controlled publish.
↗ 02 WorkflowIterate with Replit Agent without losing controlUse checkpoints and narrow requests to improve an application without destabilizing working areas.
↗Official references
Check the current product documentation.
Features, plan limits, availability, and data controls change. These official pages are the starting points used for this guide.