How to Structure your React projects

🏗️ Why Project Structure Matters in React

When your React project starts small, it's easy to keep things organized. But as it grows, messy files and random folders become a nightmare 😵. A well-structured codebase makes your project easier to maintain, scale, debug, and onboard new developers faster.

🛠️ Common Folder Structures

There’s no “one-size-fits-all” approach, but here are some widely accepted ways developers structure React apps:

📁 Basic Flat Structure (Great for Small Apps)

my-app/
├── public/
├── src/
│   ├── App.js
│   ├── index.js
│   ├── components/
│   ├── assets/
│   ├── styles/
│   └── utils/

This setup is clean and works fine for apps with limited complexity. Components are grouped in a single folder, and assets like images or fonts live in assets/.

📦 Feature-Based Structure (Best for Scaling 🚀)

src/
├── features/
│   ├── auth/
│   │   ├── AuthPage.jsx
│   │   ├── authSlice.js
│   │   └── auth.css
│   ├── dashboard/
│   │   ├── Dashboard.jsx
│   │   └── dashboardSlice.js
├── components/
├── app/
│   └── store.js
├── hooks/
├── utils/
└── index.js

Each feature is self-contained. Everything related to auth or dashboard lives in one folder. This makes collaboration and scaling easier, especially in large teams.

📁 Components Folder Structure

For shared or generic components, it’s a good practice to create a separate components/ directory:

components/
├── Button/
│   ├── Button.jsx
│   ├── Button.css
│   └── index.js
├── Modal/
│   ├── Modal.jsx
│   ├── Modal.css
│   └── index.js

This way, each component becomes its own little module—easy to read, easy to test, and easy to maintain 🧩.

📦 The “Domain-Driven” Structure

If you’re building a very large enterprise-grade app, consider a domain-oriented layout where each domain owns its state, components, routes, etc.

src/
├── domains/
│   ├── users/
│   │   ├── components/
│   │   ├── pages/
│   │   └── userSlice.js
│   ├── products/
│   │   ├── components/
│   │   └── productsSlice.js
├── shared/
├── routes/
├── services/
└── index.js

This structure allows teams to own a domain completely and work independently—very scalable for enterprise environments.

📂 Centralizing API Calls

Create a folder like services/ or api/ to organize all your backend calls. It keeps your components clean and logic separated.

// services/userService.js
import axios from 'axios';

export const fetchUser = (id) => {
  return axios.get(`/api/users/${id}`);
};

🔗 Routing Folder (Optional)

If your app has many routes, putting them all in a dedicated routes/ folder can be helpful.

// routes/AppRoutes.jsx
import { Routes, Route } from 'react-router-dom';
import Home from '../features/home/Home';
import About from '../features/about/About';

function AppRoutes() {
  return (
    <Routes>
      <Route path="/" element={} />
      <Route path="/about" element={} />
    </Routes>
  );
}

export default AppRoutes;

🧪 Where to Put Tests?

For every component or feature file, place the corresponding test file next to it with a .test.js or .spec.js suffix:

components/
├── Button/
│   ├── Button.jsx
│   └── Button.test.js

This keeps tests close to what they're testing and makes them easier to maintain.

📦 Suggested Starter Template Structure

Here’s a general-purpose structure you can use and adapt as your app grows:

src/
├── app/           # Redux store or context providers
├── assets/        # Images, icons, fonts
├── components/    # Reusable UI components
├── features/      # Feature-specific folders
├── hooks/         # Custom React hooks
├── pages/         # Route-based components (for Next.js)
├── services/      # API and external services
├── styles/        # Global and theme styles
├── utils/         # Helper functions
└── index.js

📌 Final Tips for Clean Structure

• Keep your components small and focused 🎯
• Group related files together
• Use consistent naming conventions (PascalCase for components, camelCase for files/functions)
• Modularize wherever possible

✅ Conclusion

A solid folder structure is the foundation of maintainable React code. Whether you're working solo or in a big team, investing a little time upfront in organizing your project pays off in the long run. Choose a structure that fits your app’s size and complexity—and don’t be afraid to refactor when things start feeling messy 🧹.

Happy coding! ⚛️🔥