A Complete Guide - Nextjs Project Structure Overview

Last Updated: 03 Jul, 2025   
  YOU NEED ANY HELP? THEN SELECT ANY TEXT.

Next.js Project Structure Overview

1. Root Directory

  • .next Directory: This is a build output directory, where Next.js generates static files and server-side optimizations during the build process. It should be ignored in version control (via .gitignore).

  • node_modules Directory: Contains all third-party packages your project relies on. Managed by package managers like npm or yarn and should also be ignored in version control.

  • public Directory: This is where static assets like images, fonts, and other public files reside. Files placed here are served at the root (/).

  • src Directory: While not mandatory, many projects choose to place their source files here for better organization. You can structure your app how you like, but src is a common convention.

  • pages Directory: This is the core of Next.js’s routing system. Files in this directory automatically create routes. Pages can have dynamic segments, handle API requests, and perform server-side or static generation.

    • api Directory: Inside the pages directory, you can create an api folder to handle server-side API routes. Each file in here becomes a route to be accessed by HTTP methods like GET, POST, etc.

    • Dynamic Routes: Supported by creating files with brackets in their names (e.g., [id].js). These pages can fetch data related to the route parameter.

    • Nested Routes: Automatically supported by placing files within subdirectories (e.g., pages/dashboard/index.js results in /dashboard).

  • components Directory: Typically used to contain reusable React components. Better organization helps in maintaining larger codebases.

  • styles Directory: Contains global stylesheets, CSS Modules, or any styling solution used in your project.

  • lib Directory: Keeps utility functions, configurations, or helpers that are used throughout your application.

  • hooks Directory: For custom React hooks that encapsulate side effects and logic.

2. Configuration Files

  • next.config.js: This file allows you to configure various aspects of how your Next.js application is built and served.

    • Custom Server: If needed, you can define a custom Express/Koa server with this config file.

    • Environment Variables: You can expose environment variables to the browser by prefixing them with NEXT_PUBLIC_.

    • Image Optimization: Next.js provides built-in Image Optimization that you can configure here.

    • Internationalization: Set up multiple languages and locales for your application.

    • API Proxying: Forward requests to an external API using this configuration.

3. Development Scripts

  • package.json: Manages dependencies and scripts. Typically includes scripts for:

    • dev: Runs the development server.
    • build: Builds the project for production.
    • start: Runs the production server.

  • Environment: Define environment variables in .env files (.env, .env.local, .env.development, etc.) to manage different environments like development, staging, and production.

4. Version Control

  • LICENSE: Specifies the license under which your project is released.
  • .gitignore: Lists files and directories that should be ignored by version control systems like Git, including node_modules, the build directory .next, and IDE configuration files.
  • README.md: Provides an overview of the project, setup instructions, and usage guide for new contributors.

5. Testing

  • jest.config.js: Configuration for Jest, a popular JavaScript testing framework with built-in support in Next.js.

  • setupTests.js: Can be used to run code before running your tests, like setting up mocks.

  • __tests__ Directory: Some developers prefer to place test files in this directory or alongside the components they are testing.

6. Documentation and Support

  • docs Directory: If your project requires extensive documentation, it might be organized in a dedicated docs folder.
  • CONTRIBUTING.md: Guidelines for contributing to the project, helping new developers get up to speed quickly.

Conclusion

Online Code run

🔔 Note: Select your programming language to check or run code at

💻 Run Code Compiler

Step-by-Step Guide: How to Implement Nextjs Project Structure Overview

Step 1: Setting Up a New Next.js Project

First, you will need to install Node.js and npm (or Yarn) if you haven't already done so. You can download them from npx create-next-app@latest my-next-js-app # or yarn create next-app my-next-js-app

  • Navigate into your project directory:

    cd my-next-js-app

  • Start the development server:

    npm run dev
# or
yarn dev

    • After running these commands, you should have a basic Next.js project setup and a development server running on

    Step 2: Exploring the Basic File Structure of Next.js

    When you create a new Next.js project, several files and folders are automatically generated. Here's an overview of the essential components:

    my-next-js-app/
├── node_modules/
│ └── ... (dependencies installed by npm/yarn)
├── pages/
│ ├── api/
│ │ └── hello.js
│ └── index.js
├── public/
│ ├── favicon.ico
│ └── ...
├── styles/
│ ├── globals.css
│ └── Home.module.css
├── .gitignore
├── package-lock.json (for npm)
├── yarn.lock (for yarn)
├── next.config.js
├── tsconfig.json (if using TypeScript)
├── jsconfig.json (if using JavaScript)
└── README.md

    Key Folders and Files:

    • pages/: The heart of the Next.js project. Each file here creates a route based on its name.

      • index.js: The home page of the application which maps to the root URL /.
      • api/hello.js: A sample API route. Every file in this folder is treated as an API endpoint instead of a React page.

    • public/: Contains static files like images, icons, etc. Files inside this folder can be referenced directly in your code, for example, /favicon.ico refers to public/favicon.ico.

    • styles/: Holds global and per-component CSS files.

      • globals.css: Global styles that are applied across all pages.
      • Home.module.css: Component-specific CSS scoped only to the Home component.

    • .gitignore: Lists files to ignore by git during version control.

    • package-lock.json/yarn.lock: Lock files that help ensure dependencies remain consistent.

    • next.config.js: Configuration options for your Next.js application.

    • tsconfig.json/jsconfig.json: TypeScript/JavaScript configuration for the Next.js application.

    Step 3: Creating Components

    Next.js projects use React components to build UIs. Here’s how you create and use components.

    1. Create a components folder inside the root directory:

      mkdir components

    2. Create a simple React component inside components/, say Header.js and put the following code:

      // components/Header.js
import React from 'react'; const Header = () => { return ( <header> <h1>Welcome to My Next.js App</h1> </header> );
}; export default Header;

    3. Use the Header component inside your Home page:

      // pages/index.js
import React from 'react';
import Head from 'next/head';
import Header from '../components/Header'; const Home = () => { return ( <div> <Head> <title>Home Page</title> </Head> <Header /> <p>This is the home page.</p> </div> );
}; export default Home;

    Step 4: Adding More Pages

    You can add more pages by creating additional files in the pages folder. Each filename corresponds to the URL slug.

    1. Create a about.js file inside the pages folder:

      // pages/about.js
import React from 'react'; const About = () => { return ( <div> <h1>About Us</h1> <p>This is the about page.</p> </div> );
}; export default About;

    2. Navigate to the new page by visiting in your browser.

    Step 5: Organizing Components with Subfolders

    If your project grows, you may want to organize your components into subfolders.

    1. Create a subfolder called Navigation inside components:

      mkdir components/Navigation

    2. Create a NavLink component inside the components/Navigation folder:

      // components/Navigation/NavLink.js
import React from 'react';
import Link from 'next/link'; const NavLink = ({ href, children }) => { return ( <Link href={href}> <a>{children}</a> </Link> );
}; export default NavLink;

    3. Update the Header component to use NavLink:

      // components/Header.js
import React from 'react';
import NavLink from './Navigation/NavLink';
import Link from 'next/link'; const Header = () => { return ( <header> <h1>Welcome to My Next.js App</h1> <nav> <NavLink href="/">Home</NavLink> <NavLink href="/about">About</NavLink> </nav> </header> );
}; export default Header;

    Step 6: Using Layouts

    Layouts help in consistent UI across different pages. To add layouts, you can include a higher-order component.

    1. Create a layouts folder inside the root directory:

      mkdir layouts

    2. Create a MainLayout component inside layouts/:

      // layouts/MainLayout.js
import React from 'react';
import Header from '../components/Header';
import Footer from '../components/Footer'; const MainLayout = ({ children }) => { return ( <> <Header /> <main>{children}</main> <Footer /> </> );
}; export default MainLayout;

    3. Create a Footer component inside components/:

      // components/Footer.js
import React from 'react'; const Footer = () => { return ( <footer> &copy; 2023 My Next.js App </footer> );
}; export default Footer;

    4. Wrap the pages with the MainLayout:

      // pages/_app.js
import MainLayout from '../layouts/MainLayout'; function MyApp({ Component, pageProps }) { return <MainLayout><Component {...pageProps} /></MainLayout>;
} export default MyApp;

    Step 7: Adding Dynamic Pages

    Dynamic routes in Next.js can be created using square brackets ([]) in the page filenames.

    1. Create a dynamic page called [id].js inside pages/posts/:

      mkdir pages/posts
touch pages/posts/[id].js

    2. Add content to the dynamic page:

      // pages/posts/[id].js
import React from 'react';
import { useRouter } from 'next/router'; const Post = () => { const router = useRouter(); const { id } = router.query; return ( <div> <h1>Post {id}</h1> <p>This is a post with ID: {id}</p> </div> );
}; export default Post;

    3. Visit the dynamic page by navigating to

    Step 8: Adding API Routes

    API routes allow you to create backend functionalities without setting up a separate server.

    1. Create an API route by adding users.js inside pages/api.

      // pages/api/users.js export default function handler(req, res) { res.status(200).json([ { id: 1, name: 'Alice' }, { id: 2, name: 'Bob' }, { id: 3, name: 'Charlie' } ]);
}

    2. Test the API route:

      • Visit
      • You should see the JSON data returned by the API.

    Step 9: Adding Server-Side Rendering (SSR)

    Server-side rendering allows you to fetch data at request time and pre-render the page.

    1. Modify the about.js page to fetch and display user data: 
      // pages/about.js
import React from 'react';
import fetch from 'isomorphic-unfetch'; const About = ({ users }) => { return ( <div> <h1>About Us</h1> <ul> {users.map(user => ( <li key={user.id}>{user.name}</li> ))} </ul> </div> );
}; export async function getServerSideProps() { const res = await fetch(' const users = await res.json(); return { props: { users } };
} export default About;

    Now, when you visit /about, it will fetch user data before rendering the page on the server.

    Step 10: Adding Static Site Generation (SSG)

    Static site generation generates pages at build time. For pages that don’t require fetching fresh data on each request, this method is more efficient.

    1. Create a posts page that fetches all posts and generates each post page statically:

      // pages/posts/index.js
import React from 'react';
import Link from 'next/link';
import fetch from 'isomorphic-unfetch'; const Posts = ({ posts }) => { return ( <div> <h1>All Posts</h1> <ul> {posts.map(post => ( <li key={post.id}> <Link href={`/posts/${post.id}`}> <a>Post {post.id}</a> </Link> </li> ))} </ul> </div> );
}; export async function getStaticProps() { const res = await fetch(' const posts = await res.json(); return { props: { posts } };
} export default Posts;

    2. Generate static paths for each post dynamically in the dynamic [id] page:

      // pages/posts/[id].js
import React from 'react';
import { useRouter } from 'next/router';
import fetch from 'isomorphic-unfetch'; const Post = ({ post }) => { const router = useRouter(); if (router.isFallback) { return <div>Loading...</div>; } return ( <div> <h1>{post.title}</h1> <p>{post.body}</p> <Link href="/posts"> <a>Back to posts</a> </Link> </div> );
}; export async function getStaticPaths() { const res = await fetch(' const posts = await res.json(); const paths = posts.map(post => ({ params: { id: `${post.id}` }, })); return { paths, fallback: true };
} export async function getStaticProps({ params }) { const res = await fetch(` const post = await res.json(); return { props: { post }, revalidate: 1 }; // Enable revalidation after 1 second
} export default Post;

    3. Build the project:

      npm run build
# or
yarn build

    4. Generate the static HTML files:

      npm start
# or
yarn start

    Now, when you navigate to /posts, it will display all the posts fetched at build time, and clicking a post will take you to statically generated pages for each post.

    Step 11: Final Thoughts

    This covers a comprehensive overview of how to structure a Next.js application from scratch. As you develop further, consider creating more folders to organize assets like images or media files, and configure next.config.js for advanced settings and customizations.

    For more in-depth knowledge and advanced features, refer to the

    You May Like This Related .NET Topic

    📥 Download Code ▶️ Watch Online 📖 Read Description

    Login to post a comment.