# Import/Export

## Section Brief

## UI/Workflow documentation

This section contains **general information** and **workflow documentation** about importing and exporting files with Wolvenkit. 

* For a documentation of the UI, check [Import/Export Tool](/wolvenkit/wolvenkit-app/usage/import-export/models.md):
  * [Tools: Import/Export UI](/wolvenkit/wolvenkit-app/tools/tools-import-export.md) -> [Tools: Import/Export UI](/wolvenkit/wolvenkit-app/tools/tools-import-export.md#import-tool)
  * [Tools: Import/Export UI](/wolvenkit/wolvenkit-app/tools/tools-import-export.md) -> [Tools: Import/Export UI](/wolvenkit/wolvenkit-app/tools/tools-import-export.md#export-tool)
* JSON export will generate **a text file**. If you don't know what that means, ignore this option, or read more about it under [Import/Export as JSON](/wolvenkit/wolvenkit-app/usage/import-export/import-export-as-json.md)
  * [Import/Export as JSON](/wolvenkit/wolvenkit-app/usage/import-export/import-export-as-json.md) -> [Import/Export as JSON](/wolvenkit/wolvenkit-app/usage/import-export/import-export-as-json.md#export-as-json)
  * [Import/Export as JSON](/wolvenkit/wolvenkit-app/usage/import-export/import-export-as-json.md) ->[Import/Export as JSON](/wolvenkit/wolvenkit-app/usage/import-export/import-export-as-json.md#import-as-json)
* For a detailed explanation of the different settings and their workflow, check the nested pages or use the "next" button at the bottom of the page. 

## File Structure: the `raw` folder

{% hint style="info" %}
Moving or renaming files usually breaks the import. Read on to find out why.
{% endhint %}

When exporting a resource, Wolvenkit puts the exported file into your project's `raw` folder. In the UI, you can find it in your project explorer:

The relative paths (starting under `archive`/`raw`) are the same, as will the file name (without extensions). 

#### These files are connected:

```
source/archive/base/path/your_file.mesh
source/raw/base/path/your_file.glb
```

You can import `your_file.glb` via **Import Tool**.

#### These files are **not** connected:

```
source/archive/base/path/your_file.mesh
source/raw/base/path/your_file_mesh_export.glb
```

You can **not** import `your_file_mesh_export.glb` via **Import Tool**, because Wolvenkit won't know where to put it.

## Exporting

Wolvenkit knows to ways of exporting files: [to JSON](/wolvenkit/wolvenkit-app/usage/import-export/import-export-as-json.md#export-as-json), or via the [Export Tool](/wolvenkit/wolvenkit-app/tools/tools-import-export.md#export-tool).

Exported files will be created in your project's **raw** folder. The [relative path](#user-content-fn-1)[^1] will be the same.

## Importing

Unless importing [from JSON](#import-from-json), Wolvenkit can't **create files**. 

When using the [Import Tool](#import-tool), we can only import into already existing containers (see [#file-structure](#file-structure "mention") for more information)

The easiest way to do that is: 

1. export an existing file
2. overwrite the new file in `raw` with your changes
3. import the file

### Import from JSON

This option is **in the right-click menu.**

[^1]: Path inside the game files, e.g. `tutorial\my_first_mod\meshes\my.mesh`


---

# Agent Instructions: 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:

```
GET https://wiki.redmodding.org/wolvenkit/wolvenkit-app/usage/import-export.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.