Projects & Artifacts

A project is the container for everything you build on Replit. Artifacts are the publishable outputs inside it — web apps, mobile apps, slide decks, animations, data visualizations, 3D games, and designs. When you’re building more than one thing, you have two options: add multiple artifacts to a single project, or create separate projects. The right choice depends on whether your apps share data, logic, and a deployment lifecycle. This page covers both terms in depth and shows you when to keep artifacts in a single project versus when to create separate ones.

What’s a project?

A project is the container that holds your code, data, and all the artifacts you create. When you tell Agent what you want, it sets up a project and builds the artifacts inside it. Think of a project like a workspace on your desk. Everything lives in one place and can share the same information, but each piece serves a different purpose. For example, if you ask Agent to build a fitness tracking app, it creates a project with a mobile app artifact along with the backend, database, and storage it needs to work. Key concepts:

Project: The container that holds everything — your code, data, and all your artifacts.
Artifact: A publishable output within a project (a web app, slide deck, video, and so on).
Resources: Every artifact gets automatic access to a backend, database, and file storage — no setup required.

For everything you can do with a project — manage, filter, pin, sort — see Projects.

What’s an artifact?

Artifacts are the things you can publish on Replit. Each one is a complete, standalone output that gets its own shareable URL when you publish. Everything else in your project — files, images, CSVs, code — supports your artifacts but can’t be published on its own.

Type	What it is
Web app	Websites and web applications that handle users, databases, and more.
Mobile app	Native apps for iPhone and Android.
Slide deck	Presentation decks you can present or export.
Animation	Motion graphics and animated videos. Export as MP4.
Data Visualization	Interactive dashboards and visualizations for exploring data and creating charts.
3D game	3D games, simulations, and interactive experiences.
Design	Visual directions and prototypes explored on the design canvas.

For everything you can do with artifacts — switch between them, add new ones, the Library sidebar — see Artifacts. When artifacts live in the same project, they automatically share:

Database: One artifact writes data, the others read it instantly.
Backend and API: Shared server logic, no duplicate code.
File storage: Images, documents, and uploads accessible across artifacts.
Deployment: Publishing pushes everything live together in sync.

This means you don’t need to set up connections or duplicate code between artifacts. But it also means you can’t publish one artifact without publishing the others.

Quick guide

Here are the key scenarios to consider when deciding whether to add artifacts to an existing project or create a separate one.

Use multiple artifacts in one project	Use separate projects
Apps share the same data and backend	Apps don’t share underlying logic or data
You want everything to publish together	You need independent publishing cycles
They’re complementary (like a customer app and an admin dashboard)	They’re unrelated products or for different clients
You want changes in one artifact to automatically reflect in the others	The project is short-lived, like a campaign landing page or event site

Examples

Same project: web app + mobile app for one product

A restaurant builds a web app for customers to browse the menu and a mobile app for staff to manage orders. Both connect to the same database of menu items, orders, and customer information. Why one project: the apps share the same data and backend. When a customer places an order through the web app, the staff sees it immediately on the mobile app.

Same project: app + admin dashboard + investor pitch deck

A startup builds their main product, an internal admin panel for managing content, and a slide deck for fundraising — all in one project. Why one project: the admin dashboard manages the same data the app displays, and the pitch deck can reference live metrics from the shared backend.

Separate projects: two unrelated client apps

A freelancer builds an e-commerce store for one client and a booking system for another. Why separate projects: the apps have no shared data or logic. Each client needs independent publishing and you don’t want changes to one affecting the other.

Separate projects: campaign landing page alongside a main product

You have a production app that runs year-round and a short-lived landing page for a marketing campaign. Why separate projects: the campaign page has its own lifecycle — you’ll spin it up, run it for a few weeks, and take it down. Keeping it separate avoids cluttering your main product and lets you publish or remove it independently.

Frequently asked questions

Can I move an artifact to a different project?

Not currently. If you need to separate an artifact, create a new project and ask Agent to rebuild it there.

Is there a limit to how many artifacts a project can have?

A project can contain a maximum of 7 artifacts, with a limit of 1 mobile app per project. This limit exists because additional artifacts consume more memory, which can slow down the preview. If you need more artifacts, start another project.

Can I publish just one artifact from a project?

Not currently. Publishing pushes everything live together. If you need independent publishing, use separate projects.

What's the difference between an artifact and a file?

Artifacts are things you can publish — apps, slides, videos, and so on. Files (like CSVs, images, or code) are assets within your project that support your artifacts but can’t be published on its own.

Foundations