# Import/Export: Textures WolvenKit is capable of exporting Cyberpunk XBM files to common formats like png. It will try and automatically determine the correct import settings based on the file name. {% hint style="info" %} For the UI documentation, check [tools-import-export](https://wiki.redmodding.org/wolvenkit/wolvenkit-app/tools/tools-import-export "mention") For general information such as the file structure and output directory, check [](https://wiki.redmodding.org/wolvenkit/wolvenkit-app/usage/import-export "mention") For a step-by-step workflow and troubleshooting, see [Cyberpunk 2077 Modding](https://app.gitbook.com/o/-MP5ijqI11FeeX7c8-N8/s/4gzcGtLrr90pVjAWVdTc/ "mention") -> [Textures: Importing, editing, exporting](https://app.gitbook.com/s/4gzcGtLrr90pVjAWVdTc/modding-guides/textures-and-luts/images-importing-editing-exporting "mention") {% endhint %} ## Exporting a texture from Wolvenkit 1. Add the xbm file to your project 2. Open the Export tool (Tools -> Export Tool) 3. Select your texture 4. Click "Export Selected"

This will generate a png file in your project's raw folder. ### Export Options #### XBM Export Type Choose a common image format for exported textures. Possible options (as of 8.9.1): * png * dds * tga * bmp * jpg * png #### Flip Image Vertically invert textures for convenience ## Importing textures WolvenKit is capable of importing custom images as Cyberpunk XBM files. The Import/Export Tool can replace an existing XBM or generate new standalone XBM. {% hint style="info" %} For compatibility reasons, you might want to stick to **png** files. {% endhint %} The easiest way to go about it is this: 1. Add an existing xbm file of the same type that you want to import to your Wolvenkit project. 2. [Export](#exporting-a-texture-from-wolvenkit) the xbm file: this adds a png file with the same name to your project's raw folder. 3. Overwrite the png with your edited texture. 4. Open the Import tool, and select your png file. \ \&#xNAN;*The correct settings should be applied automatically.* 5. Click "Import Selected".

### Import Options

#### Advanced Options By default advanced XBM options are hidden. This can be changed by modifying WolvenKit [**Settings**](https://wiki.redmodding.org/wolvenkit/wolvenkit-app/settings). {% hint style="warning" %} TODO: Is this still the case? Double-check! {% endhint %} #### Texture Group Select a preset for import. **This will preselect the options below**, so pick the right one for your use case! {% hint style="info" %} Wolvenkit will try to guess the right preset from your file name, so you'll want to stick to the game's naming conventions. {% endhint %}

Name
TexG_Generic_Color	Used for colour textures inside the world (for use as Textures #Diffuse/Albedo)	Transparency: from texture's alpha channel SRGB: true
TexG_Generic_Grayscale	Used for greyscale textures (for use as Textures #Roughness or metalness)
TexG_Generic_Normal	used for normal maps (for use as Textures #Normal)	No transparency Will be swizzled on import (green channel dropped), which will turn blue maps yellow
TexG_Generic_Data	???
TexG_Generic_UI	Used for UI textures that do not consider in-world lighting	like generic_color, but without isSRGB
TexG_Generic_Font	for fonts	???
TexG_Generic_LUT	for LUTs	???
TexG_Generic_MorphBlend	???
TexG_Multilayer_Color	not used for any workflows,use `Generic_Color` instead
TexG_Multilayer_Normal	not used for any workflows,use `Generic_Normal` instead
TexG_Multilayer_Grayscale	not used for any workflows,use `Generic_Grayscale` instead
TexG_Multilayer_Microblend	used for microblends	tileable normal maps with transparency for use in microblends

#### SRGB (isGamma) Sets isGamma boolean upon import. Color textures (such as diffuse) must be set as true, or they will appear blown-out or too bright in-game. #### VFlip (Default: True) Should the image be v-flipped? {% hint style="warning" %} The game saves images as upside-down. Wolvenkit will fix that for you, so unless your texture is already flipped, you'll want to leave this alone. {% endhint %} #### RawFormat *as of 8.9.1* Raw format for export. Possible values are: * TRF\_Invalid * TRF\_TrueColor * TRF\_DeepColor * TRF\_Grayscale * TRF\_HDRFloat * TRF\_HDRHalf * TRF\_HDRFloatGrayscale * TRF\_Grayscale\_Font * TRF\_R8G8 * TRF\_R32UI * TRF\_Max #### Generate MipMaps Should [MipMap](https://en.wikipedia.org/wiki/Mipmap)s be created? {% hint style="warning" %} The \ This requires the texture width and height to be potencies of 2! {% endhint %} #### IsStreamable ??? #### Transparency from Alpha Channel (formerly PremultiplyAlpha) Should the image consider **transparency**? {% hint style="info" %} Transparency must be read from a png's alpha channel. If you don't know how to create one, see the guide about texture editing on [the yellow wiki](https://app.gitbook.com/s/4gzcGtLrr90pVjAWVdTc/modding-guides/textures-and-luts/images-importing-editing-exporting). {% endhint %} --- # 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/textures.md?ask= ``` 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.