Published on

React TypeScript Folder Structure To Follow

  • Name

Hey Front-End explorers, this is the folder structure we currently incorporated in our project. Please feel free to restructure your folder structure as you will and do let me know if you know a better Folder structure to organize your React project.

Folder Structure


  • In the components folder, we are expected to define components that will be used to create pages.
  • We can define the following component types in the components folder.

For Example: Footer.tsx, UserProfile.tsx, Modal.tsx, Drawer.tsx

  • Extension for React component file should be .tsx

For Example: Footer.tsx

Footer Component and components folder structure:

  • Use the Folder name as the component name.

For Example: Footer.tsx should have a reference name of Footer.

Footer Component File:

  • Define index.tsx for the components folder, which act as the single access point for that component.

Footer Folder’s index.tsx file

🔷 Good Practice 🔷

  • Only include one React component per file.
  • Generally, a file can contain any number of components as you’d like. However, keeping components in their respective file keeps things organized.
  • Makes it very clear which imports/styles etc are used by which component.


  • Reusable custom hooks should be kept in the src/hooks folder.
  • Name the hooks by prefixing them with use and then its functionality all in camelCase.

hooks Folder and File Name:


  • In a React TypeScript project, the “pages” folder is often used to organize components that represent different pages or views of the application.
  • This folder is part of a common project structure used in React applications to promote modularity, maintainability, and scalability.

pages folder and it’s component structure:


  • “types” folder provides a centralized location for storing all type & enum definitions related to the application. This organization makes it easier for developers to locate and manage different types without cluttering the main codebase.
  • In case the types are specific to a component or a Page then we can create a nested folder under “types” folder.
  • Name your types as your Component, Prop or State name in camelCase followed by “.types.ts”

For Example: buttonProps.types.ts, myComponent.types.ts

types folder structure:

🚨_Watch Out_🚨

  • Do not use *.d.ts files for defining types.
  • d.ts files do not modularize the types defined in them, they put the types in the global scope of the application.

Reference: Youtube Video on Why not to Define types in d.ts

Do ✅

export type MyComponentPropsSubItem = {  
    label: string;  
    value: string | null;  
export type IssuerInformationProps = {  
  [category: string]: Array< MyComponentPropsSubItem >;  


  • The utils folder will help us organize the helper function that we use throughout our application
  • I agree that not all helper functions will be shared across the application. However, we can make a folder for the component in utils and create the helper function there.
  • And for all the shared helper functions we can keep them in the utils directory itself.

utils folder structure:

api & services:

  • use this folder structure to define your api definition using axios or fetch.
  • services folder should be used to call api to fetch desired data.

api & services folder structure:


  • This folder holds app-wide constants such as app data.
  • The naming convention to define data files would be the name of the component and extension as “.data.ts”.

constants folder structure:


  • assets folder should be used to store icons and images.

assets folder structure:

🔷 Good Practice 🔷

  • Images, icons, or other component-specific assets should be placed directly into the assets folder.
  • If using images then try to use WebP extension images.
  • These images are smaller in size compared to JPG, JPEG, or PNG
  • Moreover, use SVG for icons.


  • In the styles folder, we will define global styles, variable names, mixins, and functions that will be used across the application.

styles folder structure:

I will update the article if I find any better way of structuring the folders. If this was in any way helpful please leave a clap 👏 and follow 🚶‍♂️for more such content.