> For the complete documentation index, see [llms.txt](https://tools.continis.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tools.continis.io/scene-notes/other/data-and-folders.md).
# Data and folders
Since Scene Notes is a purely project-based tool, the data for the notes is stored in a specific folder as ScriptableObjects. The location of this folder is initially **Assets > SceneNotes**, but it can be changed in [Project Settings](/scene-notes/other/project-settings.md).
## Data format
Inside the main folder, alongside the NoteCategories ScriptableObject, multiple folders will be created with the guid of each scene that contains notes:
As notes are moved between scenes, these folders will be automatically created and destroyed, so you don't need to manage them.
Inside these scene folders, each ScriptableObject represents a note:
The file name reflects the note's title and is automatically updated when the title changes.
When the toolbar is open, what is visualised in the scene are **invisible GameObjects** that reference these ScriptableObjects. Deleting one of these GameObjects **will not** delete the ScriptableObject.
{% hint style="info" %}
It is advisable to [delete a note](/scene-notes/using-the-tool/creating-and-editing-notes.md#deleting-a-note) by clicking on the trash button in the note's Inspector.
{% endhint %}
Though notes are generally meant to be managed from within the Scene View, it is totally possible to manage them directly from their ScriptableObjects: changing properties, assigning different scenes, etc.
However, after making these changes, it's good practice to [reload the notes](/scene-notes/using-the-tool/visualising-notes.md#bringing-up-the-interface) from the Overlay so they show correctly in the Scene View.
### Screenshots
Screenshots taken from a note are stored in one of two ways, controlled by the **Save Screenshots as Sub-assets** option in Project Settings.
When the option is **enabled** (the default), each screenshot is saved as a sub-asset inside the note's own `.asset` file. This keeps the screenshot tightly bound to the note: it can't be referenced from anywhere else in the project, it's hidden from the Texture2D object picker, and it is automatically deleted when the note is deleted. The trade-off is that the texture is stored uncompressed inside the `.asset`, so the file grows in size and git diffs grow with it.
When the option is **disabled**, screenshots are saved as standalone PNG files on disk, under the Notes folder, in a dedicated subfolder structure:
```
/Screenshots///Screenshot_.png
```
This mirrors the per-scene layout already used for notes themselves: each scene gets its own folder (named after the scene's GUID), and within it, each note gets its own folder (named after the note's GUID). Files saved this way retain PNG compression on disk, which keeps the project lighter and produces smaller git diffs, at the cost of the screenshot files being independent assets that aren't cleaned up automatically when the note is deleted.
Both modes can be mixed within the same project: changing the setting only affects screenshots taken from that point on, and existing screenshots remain wherever they were originally saved.
## Version control
As notes are meant to be shared across the team, the folder containing the Scene Notes should be versioned using the version control of your choice. This way changes to the notes can be pushed and pulled just like any other regular file.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://tools.continis.io/scene-notes/other/data-and-folders.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.