# GShade: a ReShade fork with a control panel and a preset converter

> GShade is a heavily modified ReShade fork that ships as a Windows installer with a control panel, a preset converter that reads configurations from nine predecessor packages, and settings autodetection for over 300 games. The shaders are HLSL, and the repository is a library of them rather than the tool itself.

**Mortalitas/GShade** — GShade is a highly modified ReShade fork & utility package with numerous improvements and settings autodetection for over 300 games.

- Repository: https://github.com/Mortalitas/GShade
- Website: https://www.gshade.org
- Stars: 534 · Forks: 112
- Language: HLSL
- License: NOASSERTION
- Published: 2026-10-22 · Updated: 2026-10-22 · Language: en
- Canonical page: https://hysenlabs.com/projects/mortalitas-gshade

## A ReShade fork where the extra features are the point

GShade is described as a highly modified ReShade fork and utility package with numerous improvements and settings autodetection for over 300 games, and the fork relationship is stated in the first line of the documentation.

ReShade is the post-process shader injector that sits between a game and the graphics driver. GShade takes that base and changes it, and the changes are substantial enough that the shaders cannot be assumed to work elsewhere.

That caveat is stated up front and it is the most important line in the whole document. All shaders in the repository are intended for use with the latest GShade release, and not all shaders will work under official builds of ReShade, due to the implementation of GShade's additional features. The documentation points at both the repository licence and the individual file licences for questions about distribution and modification.

So there are two separate licensing questions and the documentation is careful to keep them apart. The repository licence governs the fork and the utility package, while each shader file carries its own licence, and the note about referring to both is there precisely because a shader from this repository may be redistributed on different terms from the tool around it.

The project is written primarily in HLSL, which is the shader language, and the licence is a custom one that GitHub could not classify, with the terms in a LICENSE.md file. The homepage is www.gshade.org, the last push was on 2026-09-27, and the recent releases are v5.2.3, v5.2.4 and v5.2.5, all in 2026. The release names carry a word each, forming a phrase across the three tags.

What GShade adds over the base is not enumerated in the documentation available here, and the honest summary is that the difference is characterised rather than itemised. The Quick Reference is linked as the place to learn about the unique features, and it is hosted on Google Drive rather than in the repository.

## The repository is a shader library, not the tool

The top level listing makes the split between the fork and the content explicit, and it is worth reading closely.

There are ComputeShaders/, Fonts/, Shaders/ and Textures/ directories, a GShade.ini file, a notification.wav file, the LICENSE.md and the README.md.

The GShade.ini is the configuration file, which is the thing ReShade installations are expected to have and which is where settings live. The notification.wav is the sound the tool plays, which is a small detail that tells you the installer is a desktop application rather than a bare shader folder.

The four content directories are the substance of what a user actually wants. Shaders/ holds the effects themselves, ComputeShaders/ holds the compute shader variants, Textures/ holds the images the effects need, and Fonts/ holds the font files the overlays use. A post-process shader package is not just code, because most shader effects that add an interface or a colour grade also need textures and typefaces to draw with.

That division is the practical answer to how a shader package is shared. A preset that a user downloads references a shader file, and the shader file references a texture, and the texture references a font. The package has to be laid out so that those references resolve on someone else's machine, which is why the top level is a fixed set of directories rather than a flat collection of files.

The other thing the listing tells you is where the fork itself lives, which is not here. The repository contains the shaders and the configuration, and the executable that loads them is distributed as a Windows installer from the releases page, with the latest one linked as a direct download at a fixed path.

## Two installers, one for Unix and one recommended for Mac

Installation is handled by separate projects, and the documentation treats the Mac case as special enough to need its own command.

For Linux and Unix the official installation script is in a separate repository, and the documentation recommends running it via this command in your terminal of choice:

```sh
bash -c "$(curl -fsSL https://raw.githubusercontent.com/Mortalitas/GShade-Bash-Installer/master/gshade_installer.sh)"
```

For Final Fantasy XIV on Mac, the documentation recommends installing a specific Mac build of the game first, and notes that the community behind it does not provide support for GShade. After that you use the same script, run through the Terminal app rather than a Unix shell:

```sh
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Mortalitas/GShade-Bash-Installer/master/gshade_installer.sh)"
```

The difference between the two commands is the shell that interprets them. One pipes the script into a shell directly and the other invokes a specific binary path, which is what the Terminal app needs to run a script that assumes a POSIX shell is present.

The Mac instruction is doing two things at once. Installing the community game build first is a prerequisite rather than a GShade step, because a wrong order there produces a confusing failure. And the explicit note that the community does not support GShade is a pointer for where to take problems that turn out to be about the game installation rather than about the shaders.

For Windows the distribution is a single installer executable from the releases page, linked at a stable path so that the URL does not change with each version. There is no mention of a script for that platform, which matches the shape of the tool: the Windows build is a desktop application with a control panel, and the Unix side is a script that sets up the equivalent arrangement.

## The installer brings a control panel and a preset converter

The list of what the installer version includes is the best description of how the project distinguishes itself from plain ReShade, and it is longer than a feature list usually is.

Multi-language support is there, with the installer shipping in English, Japanese, Korean, German, French, Italian and one further language. The set is chosen rather than incidental, because it maps onto where the player base for these games is.

Then there are the community presets, which is a distribution decision as much as a feature. The project collects presets made by its community and bundles them, which means a new user gets a working configuration rather than an empty effect stack.

The control panel is the part that matters most, and it has three named components. One-click Updates is the first. Individual Installation Management is the second, which is the feature that makes a fork practical to run: a user with several games and several shader configurations needs to see what is installed where and be able to manage each one separately. And the Preset Converter is the third, and it converts presets from a long list of predecessors: ReShade 3, ReShade 4, ReShade 5, Stormshade, MoogleShade, HQ Shade, Dark Veil, Faeshade and Potoatoshade.

That converter list is a history of the ecosystem in one place. Each entry is a shading package that people have presets for, and the converter means a user arriving from any of them can bring their configuration rather than starting again. A fork that only converted from ReShade would leave the people arriving from Stormshade or MoogleShade behind, and those are exactly the users who have deeply customised presets.

The rest of the installer contents are smaller. Vulkan Toggles, an optional desktop update reminder, and an uninstaller.

The uninstaller deserves a note, because it is a marker of how the project sees itself. A shader injector is an invasive install: it hooks into the graphics pipeline and it writes configuration into the game's directory. A tool that ships an uninstaller is acknowledging that it has that character, and it is unusual to see one listed as a feature rather than assumed.

## The game list, and the two exceptions that stand out

There is a long list of games people are seen using GShade with, and it is worth reading as a compatibility statement rather than as a list of endorsements.

The framing sentence is careful: while GShade can work with any game that ReShade does, the following are some of the more common games seen being used with GShade. So the list is examples, not a whitelist.

The names cover the usual post-process shader audience. Black Desert Online, City of Heroes, DC Universe Online, Dragon Nest, Elder Scrolls Online, Fallout 76, Final Fantasy XIV, Guild Wars 2, Marvel's Avengers, Neverwinter, Phantasy Star Online 2 New Genesis, Shroud of the Avatar, Star Wars: The Old Republic, The Sims 4, Tree of Savior, Warframe and World of Warcraft, along with World of Warcraft Classic.

Several entries carry a qualifier that changes how you should read them. Monster Hunter Rise requires REFramework, so it is not a plain install. Second Life is listed with the names of its viewers, which are the official one plus Alchemy, Black Dragon, Catznip, Firestorm, Genesis, Kokua and Singularity, and the practical meaning is that the shader has to work across a range of forks of the same client.

Two entries are for platforms rather than games. Java appears, with the note that it is for Java-based games such as Minecraft, which is a different integration path entirely from a native game, since the injector has to attach to a virtual machine rather than to a Direct3D or Vulkan process. And FiveM appears, which is the multiplayer framework used by a large number of modification projects.

NeosVR and City of Heroes sit alongside the mainstream titles, and the presence of City of Heroes is a good sign about the age of the audience, since it is a game from the same era as the earliest versions of ReShade.

The autodetection claim in the project description, settings autodetection for over 300 games, is the number that connects the two lists. The list above is the visible set of common ones, and the autodetection covers a much larger set, which is what makes the tool work on a game nobody has written about.

## Conclusion

GShade suits a player who wants a working shader setup across several games without maintaining each one by hand, since the control panel, the updater and the converter cover the three chores that make running a fork tedious. It does not suit you if you intend to redistribute the shaders yourself without reading the per-file licences, and the documentation is explicit that GShade's own shaders are not interchangeable with official ReShade builds. Before you install it, check which licence applies to what you plan to share, and if you are on Mac with Final Fantasy XIV, follow the order the documentation gives, because installing the community game build first is a prerequisite rather than an optional step.

## FAQ

### What is GShade and how does it relate to ReShade?

GShade is a highly modified ReShade fork and utility package with numerous improvements and settings autodetection for over 300 games. The fork adds features that are not in official ReShade, which is why the shaders in the repository are intended for the latest GShade release and not all of them work under an official build.

### How do I install GShade on Linux or Unix?

Use the official installation script from the GShade-Bash-Installer repository, run with bash -c on a curl of the script URL. For Final Fantasy XIV on Mac the documentation recommends installing the community Mac build of the game first, then running the same script through the Terminal app with an explicit /bin/bash invocation.

### What does the GShade installer include besides the shaders?

Multi-language support in seven languages, community created presets, and a control panel with one-click updates, individual installation management and a preset converter. The converter handles presets from ReShade 3, ReShade 4, ReShade 5, Stormshade, MoogleShade, HQ Shade, Dark Veil, Faeshade and Potoatoshade. It also includes Vulkan toggles, an optional desktop update reminder and an uninstaller.

### What licence applies to GShade and its shaders?

Two separate questions. The repository licence is a custom one recorded in LICENSE.md, and individual shader files carry their own licences, so the documentation points at both for questions about distribution and modification.

### Which games does GShade support?

Any game ReShade works with, since the fork keeps that base. The documentation lists the more common ones, including Elder Scrolls Online, Final Fantasy XIV, The Sims 4, Warframe, World of Warcraft and Monster Hunter Rise, which additionally requires REFramework, plus Second Life across its named viewers and Minecraft through Java.

## Sources

- [Issues](https://github.com/Mortalitas/GShade/issues)
- [Mortalitas/GShade on GitHub](https://github.com/Mortalitas/GShade)
- [Project website](https://www.gshade.org)
- [README](https://github.com/Mortalitas/GShade/blob/master/README.md)
- [Releases](https://github.com/Mortalitas/GShade/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/mortalitas-gshade