Your new Astro project generated from the
create astro CLI wizard already includes some files and folders. Others, you will create yourself and add to Astro’s existing file structure.
Here’s how an Astro project is organized, and some files you will find in your new project.
Directories and FilesSection titled Directories and Files
Astro leverages an opinionated folder layout for your project. Every Astro project root should include the following directories and files:
src/*- Your project source code (components, pages, styles, etc.)
public/*- Your non-code, unprocessed assets (fonts, icons, etc.)
package.json- A project manifest.
astro.config.mjs- An Astro configuration file. (recommended)
tsconfig.json- A TypeScript configuration file. (recommended)
Example Project TreeSection titled Example Project Tree
A common Astro project directory might look like this:
src/ folder is where most of your project source code lives. This includes:
Astro processes, optimizes, and bundles your
src/ files to create the final website that is shipped to the browser. Unlike the static
public/ directory, your
src/ files are built and handled for you by Astro.
Some files (like Astro components) are not even sent to the browser as written but are instead rendered to static HTML. Other files (like CSS) are sent to the browser but may be optimized or bundled with other CSS files for performance.
Section titled src/components
Components are reusable units of code for your HTML pages. These could be Astro components, or UI framework components like React or Vue. It is common to group and organize all of your project components together in this folder.
This is a common convention in Astro projects, but it is not required. Feel free to organize your components however you like!
Section titled src/content
src/content/ directory is reserved to store content collections and an optional collections configuration file. No other files are allowed inside this folder.
Section titled src/layouts
src/components, this directory is a common convention but not required.
Section titled src/pages
Pages are a special kind of component used to create new pages on your site. A page can be an Astro component, or a Markdown file that represents some page of content for your site.
Section titled src/styles
It is a common convention to store your CSS or Sass files in a
src/styles directory, but this is not required. As long as your styles live somewhere in the
src/ directory and are imported correctly, Astro will handle and optimize them.
Section titled public/
public/ directory is for files and assets that do not need to be processed during Astro’s build process. These files will be copied into the build folder untouched.
This behavior makes
public/ ideal for common assets like images and fonts, or special files such as
public/ directory, but be aware that those files will not be bundled or optimized in your final build.
Section titled package.json
npm run build).
There are two kinds of dependencies you can specify in a
devDependencies. In most cases, these work the same: Astro needs all dependencies at build time, and your package manager will install both. We recommend putting all of your dependencies in
dependencies to start, and only use
devDependencies if you find a specific need to do so.
For help creating a new
package.json file for your project, check out the manual setup instructions.
Section titled astro.config.mjs
This file is generated in every starter template and includes configuration options for your Astro project. Here you can specify integrations to use, build options, server options, and more.
See the Configuring Astro Guide for details on setting configurations.
Section titled tsconfig.json
This file is generated in every starter template and includes TypeScript configuration options for your Astro project. Some features (like npm package imports) aren’t fully supported in the editor without a
See the TypeScript Guide for details on setting configurations.Learn