dxvk.conf: where to put it, what to write, and how to check it works

What dxvk.conf is (and is not)

A plain text file that DXVK reads when a game starts. It changes only what DXVK does, never the game’s own settings. It is optional: DXVK has built-in settings for 263 profile entries (262 in g_profiles plus one for Steam Deck, counted from its source at 3.1.1), so many games need no file at all. There is no dxvk.ini, dxgi.ini or registry setting: if a guide mentions one, it means dxvk.conf.

Where to put dxvk.conf

The rule: the game’s working folder, at the moment it creates its Direct3D device. In every one of our tests that was the folder holding the .exe, and DXVK logged that it found the file there (F23).

Windows: next to the game’s .exe

The folder name is an example: use the folder of the exe your game really runs.

Games with launchers or a bin folder

The file goes beside the real game program, not the launcher. Some games keep it in a subfolder, for example a Bin folder. Open Task Manager, right-click the running game, choose Open file location, and use that folder. The Game Checker also tells you launcher from game.

Linux, Proton and Steam Deck

The same rule applies inside the prefix, or you can name a file anywhere with DXVK_CONFIG_FILE=/path/to/file.conf in the launch options. A file named there that does not exist is not an error: the game just runs with defaults, so a typo in the path fails silently (F30).

Program Files and permissions

Writing into C:\Program Files needs administrator approval. With “file name extensions” hidden, Notepad may save dxvk.conf.txt: turn extensions on in File Explorer (View, Show, File name extensions) and check the name. We could not take desktop screenshots of these steps, and we did not test whether Windows redirects writes to a VirtualStore folder.

Build one

How to write it

One option per line, as key = value. A line starting with # is a comment. Booleans are True or False, strings go in double quotes, numbers are plain. The part before the dot says which API the option affects.

One file for several games: per-game sections

A line like [GameName.exe] applies the lines below it to that exe only. We proved it: an option under [dxprobe64.exe] changed the game’s feature level, and the same option under another exe name was ignored (F24). Matching is on the exe file name; upstream says wildcards are not supported. Useful for one shared file on Linux or a folder with several programs.

Check that DXVK read it

Run the game, close it, then open the log. On Windows it is <exe>_d3d9.log or <exe>_d3d11.log next to the exe (F13); under Wine it is the terminal output, or a file if you set DXVK_LOG_PATH (F14). This is what our Windows run showed with dxvk.maxFrameRate = 60:

          1
          info:  Game: dxprobe64.exe
          
          
          
        
          2
          info:  DXVK: v3.1.1
          
          
          
        
          3
          info:  Build: x86_64 gcc 16.2.0
          
          
          
        
          4
          info:  Found config file: dxvk.conf
          
          
          DXVK found and read the file.
        
          5
          info:  Effective configuration:
          
          
          
        
          6
          info:    dxvk.maxFrameRate = 60
          
          
          The option it applied. If your option is missing here, it was ignored.
        

Setting options without a file: DXVK_CONFIG and DXVK_CONFIG_FILE

DXVK_CONFIG takes the same lines separated by semicolons; DXVK_CONFIG=d3d9.maxFrameRate=30 gave 28.3 FPS in our test (F22). DXVK_CONFIG_FILE names a file, and a missing file is silent (F30). On Linux set them in Steam launch options, for example DXVK_CONFIG=“dxvk.maxFrameRate = 60” %command%, or in your launcher’s environment fields. On Windows a system-wide variable affects every DXVK game, so prefer the file. See environment variables.

Recipes people actually use

For game-specific files, see the game guides.

Options that stopped working

Common mistakes