# Ignition internal Folder Structure **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [September 17, 2025, 2:55pm UTC](https://forum.inductiveautomation.com/t/ignition-internal-folder-structure/110717 "2025-09-17T14:55:49Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [September 17, 2025, 3:58pm UTC](https://forum.inductiveautomation.com/t/ignition-internal-folder-structure/110717/2 "2025-09-17T15:58:54Z")
I thought we had some kind of reference page for this in the manual, but all I found was this, which is not quite the full story: > **[resource.json File | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.3/appendix/reference-pages/resource-json-file)** > > This page describes the contents on resource.json files This old post of mine goes into more detail, though is a bit out of date: > [@Source control in Ignition 8](https://forum.inductiveautomation.com/t/source-control-in-ignition-8/26886/2): > > All project resources are located in the gateway installation directory (if you're on, say, Windows, this defaults to Program Files/Inductive Automation/Ignition/. From there, project resources are in /data/projects/. Each project will have a folder there, and all resources within that project are then separated into modules. Below each module is a folder structure representing the path that you see in the designer. An individual resource is itself a folder, containing at minimum two files: a r… Basically: `projects/` has an ignorable `.resources/` folder. All other folders in `projects/` will be scanned - if they contain a valid `project.json` manifest, then they make up an Ignition project. The name of the project will be the literal name of the folder on disk. Below each project directory, the next folder is the module ID, and the folder below that is the resource type ID. Those two folders make up a unique identifier for every Ignition project resource. After that `moduleID/typeID/` folder pair, things split into two paths. If there is a `resource.json` file, then it is a so-called "singleton" resource - there can be either zero or one of any given singleton resource, and they have no name. If there are any folders, they define the path to the given resource, ending with a folder that becomes the resource name and contains a `resource.json` file in it. That `resource.json` file is described in the manual page linked above, but the most important entry is the `files` array that tells the resource system about the other files on disk. So putting it all together: `data/projects/Test/ignition/global-props/resource.json` Is the path to a manifest file for the `global-props` resource (owned by the core Ignition platform, not any module) in a project named `Test`. `data/projects/CoolProject/com.inductiveautomation.perspective/views/myView/resource.json` Is the path to a manifest file for the `myView` Perspective view in a project named `CoolProject`. By contrast, `data/projects/CoolProject/com.inductiveautomation.perspective/views/myFolder/myView/resource.json` Is the path to a manifest file for a view `myView` inside a folder `myFolder` in the same project. The **short** answer to your question is: Everything in that directory is important to you _except_ the `.resources/` folder. --- _[View the full topic](https://forum.inductiveautomation.com/t/ignition-internal-folder-structure/110717)._