> For the complete documentation index, see [llms.txt](https://wiki.redmodding.org/cyberpunk-2077-modding/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/textures-and-luts/making-custom-microblends.md).

# Making Custom Microblends

How to create custom microblends.

**This guide was originally written by Halk and imported with their permission. You can find the original**[ **here**](https://docs.google.com/document/d/1oRjXHE08oDnaKwvgEOKxl0gZGkBADgSn2azCRwUeQLs/edit)**.**

The easiest/quicker way to make custom microblends is to have access to Photoshop and use ready-to-go seamless patterns. I like to look for these in [Pixabay](https://pixabay.com/images/search/seamless%20pattern/) and [Vecteezy](https://www.vecteezy.com/search?qterm=seamless-pattern-free\&content_type=vector).

You can try making your own seamless pattern with the help of [this tutorial](https://www.youtube.com/watch?v=uB0IG2x2wPc) (for Photoshop).

1. After you download or make your pattern, make sure it’s a 1:1 seamless image. I recommend working on at least 1k (1024x1024) to keep the quality.

![](https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-9c999218111394bda4f7c24123fce1508970dbba%2F0.png?alt=media)

2. Turn everything you **don’t** want as microblend into transparency. You can magic wand if you’d like, but a quick way to do it is using the Color Range tool in PS. In my case, I’ll get rid of the grey areas.

![](https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-cd74f3326f29ca1a524b5328310e87333575c44c%2F1.png?alt=media) ![](https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-20b8b5102ac7e9748baf854b67b3878817f1107f%2F2.png?alt=media)

Upper menu: Select > Color Range > Use the eyedropper to select the color you want gone.

Change the Fuzziness to make it as clean as possible.

3. Lock the transparency on this layer, then fill or paint the pattern with **THIS PURPLE (#7f7fff)**.

![](https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-9003ef8df71e2fc6988c6eb9b8dc2d8946b69bbb%2F3.png?alt=media)

If set up like this, it will be a one color microblend. To make two or more colors, separate the elements you want and save multiple files to go into different layers of the mlsetup. For example:

![](https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-6032c244294538ccd2d5c8f6d97048ecffccde99%2F4.png?alt=media)

4. Save the file(s) as .png and use WolvenKIt to [import your png file](/cyberpunk-2077-modding/modding-guides/textures-and-luts/images-importing-editing-exporting.md#importing-a-texture) **with transparency** over a basegame file, e.g. **`base\surfaces\microblends\scratches_and_flakes_a.xbm`.**
5. Now simply custom-path your microblend(s) while making sure to path them into the **µblends** window on MlsetupBuilder OR in the microblend path in the .mlsetup on WolvenKit.

![](https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-6ec9efd1d9ceb2a48fc55e02df2c2432bd08d6ea%2F5.png?alt=media)

![](https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-afd7f9f795ea4f58478eba8a7277f0e6cf7f6fe4%2F6.png?alt=media)

**IMPORTANT:** if you’re adding microblends into a custom port, don’t forget to make the microblend layer in the mlmask a neutral grey, otherwise it’ll screw with the microblend color. For me, the **50% grey (#959595)** from PS works perfectly.

![](https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-fe7e379286023d29685ae43ded4b76785e272904%2F7.png?alt=media)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/textures-and-luts/making-custom-microblends.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.