Skip to main content
Environment variables are key-value pairs passed into the Linux/Wine runtime when a container starts. They let you control low-level behavior of Mesa graphics drivers, Wine internals, DXVK, and other subsystems without recompiling anything. Each variable is stored in the envVars field of a container’s .container config file. The EnvVars class parses them as a space-separated list of KEY=VALUE pairs:
To add or edit variables, open Container Settings → Environment Variables tab.
Variables are applied at container startup. Restart the container after making changes for them to take effect.

Default environment variables

Every new container is initialized with the following defaults (from Container.DEFAULT_ENV_VARS):

Additional useful variables

Prevents Mesa from advertising OpenGL extensions that were introduced after the given year. Some older games crash or refuse to start when they detect modern extensions they were never written to handle. Setting this to 2003 is recommended for games from the early 2000s.
Add this variable in Container Settings → Environment Variables if an older game fails to open.
Controls which Wine debug channels are logged. The default channels configured in Winlator Settings are warn, err, and fixme. You can narrow or broaden the output:Enable Wine debug logging in Settings → Enable Wine Debug, then choose channels from the list.
Enables asynchronous shader compilation in DXVK. Shaders are compiled in the background instead of blocking the main thread, which eliminates the most severe stutters during first-run shader compilation. Some games may show brief graphical artifacts while a shader is still compiling.
Overlays DXVK performance information on-screen. Common values:

Format reference

The EnvVars class (see EnvVars.java) parses the variable string as follows:
  • Entries are space-separated: KEY1=VALUE1 KEY2=VALUE2
  • No quotes are needed for simple values
  • Values with spaces must escape the space with a backslash (\ ) in the stored string (handled automatically by the UI)
  • Duplicate keys are overwritten; the last definition wins
  • The full list can be retrieved as a String[] via toStringArray() or as a single escaped string via toEscapedString()
Do not add line breaks inside the environment variable field. All entries must stay on a single logical line, space-separated.