The DOSBox Config File: Where It Is and How to Edit It
dosbox-0.74-3.conf and sits in your own user folder, under AppData\Local\DOSBox โ the easiest way to open it is the Options entry in the DOSBox Start Menu folder. On Linux it is ~/.dosbox/dosbox-0.74-3.conf. On a Mac it is the file named DOSBox 0.74-3 Preferences inside ~/Library/Preferences. Open it with any plain text editor, change the line you need, save, and start DOSBox again.
Honest labels, up front. Everything on this page is copied from the DOSBox manual, the DOSBox Wiki, and โ in one clearly marked section โ the DOSBox Staging manual, which describes a different program and is never blended with the DOSBox 0.74 directions. Nothing here was tested by playing a game for this page: the DisBox settings collection this page belongs to holds 0 settings verified by actual play.
These settings are part of the DisBox collection. DisBox OS โ the system being built to run games with settings like these โ is in the works; its interface comes first, so there is no finished OS to download yet.
Where the file is, system by system
The manual (section 13, “The configuration (options) file”) says the file “is automatically created the first time you run DOSBox,” and gives the home of each system’s copy:
- Windows: reach it through the Start Menu โ “All Programs” → DOSBox-0.74-3 → Options. The DOSBox Wiki’s dosbox.conf page gives the folder behind that shortcut. On Windows Vista, 7 and 8.x it is
{system drive}:\Users\{username}\AppData\Local\DOSBox\dosbox-{version}.conf; on Windows XP it was%USERPROFILE%\Local Settings\Application Data\DOSBox\dosbox-{version}.conf. The Wiki also notes the DOSBox Status Window shows the location when DOSBox starts. - Linux:
~/.dosbox/dosbox-0.74-3.conf. - Mac OS X:
~/Library/Preferences/DOSBox 0.74-3 Preferences.
One warning from the manual matters more than any path: on Windows Vista and 7, “the configuration file won’t work correctly if it is located in ‘Windows’ or ‘Program Files’ folder or their subfolders, or directly on c:\” โ so if a guide told you the config file lives inside the DOSBox program folder under Program Files, that guide is sending you to the wrong file. The manual’s own suggestion for extra config files is a folder of your own, for example C:\oldgames. On 0.74, the Wiki adds, you can open the configuration file by opening DOSBox 0.74 Options.bat in the DOSBox folder.
How the file is written
The manual’s description is short and complete: “The file is divided into several sections. Each section starts with a [section name] line. The settings are the property=value lines where value can be altered to customize DOSBox.” Lines starting with # and % are comment lines โ notes for you, ignored by DOSBox. The sections you will meet most are [sdl] (the window and fullscreen), [cpu] (speed), [mixer] and the sound sections, [dos] (memory switches like XMS and EMS), [ipx] (network play), and [autoexec] โ lines at the end of the file that DOSBox runs as DOS commands every time it starts, so a game can mount its folder and start itself.
Edit with a plain text editor (Notepad is fine). Change only the part after the = on a line, keep the section headers exactly as they are, save the file, and restart DOSBox โ most settings are read when DOSBox starts.
One file per game
Different games want different settings, and DOSBox is built for that. The Wiki’s recommendation: “define a conf file for each game that will set the appropriate configurations and start the game for you. Then, create a shortcut such as DOSBox.exe -conf "DOSboxGameName.conf".” The Wiki describes the file as one DOSBox can use “globally and/or locally per game (and settings that are left out are taken from the global file)” โ so a per-game file only needs the handful of lines that game cares about.
The manual gives the load order. DOSBox loads the configuration files named with -conf. If none were specified, “it will try to load ‘dosbox.conf’ from the local directory. If there is none, DOSBox will load the user configuration file. This file will be created if it doesn’t exist.” That order explains the classic confusion: if your edits to the user file seem to do nothing, check whether a dosbox.conf is sitting in the folder you started DOSBox from โ it is read first.
You can also work from inside DOSBox. The built-in CONFIG program (on DOSBox’s own Z: drive) writes the current settings out to a file โ the manual’s example is:
config -writeconf c:\dosgames\dosbox.conf
The same program can change a setting while DOSBox runs (config -set "cpu cycles=10000" is the manual’s example) or report a current value (config -get "cpu core"). The manual notes that doing per-game setups with separate configuration files “may be easier” than batch-file tricks with -set and -get, but both routes are documented.
If you run DOSBox Staging instead
DOSBox Staging is a separate program with its own arrangement, printed here from its own manual and not blended with the directions above. Its main file is called dosbox-staging.conf โ on Windows it lives at C:\Users\%USERNAME%\AppData\Local\DOSBox\dosbox-staging.conf โ and it is created automatically with default settings the first time Staging starts, if it does not exist. On top of that, a file named dosbox.conf in Staging’s working folder is loaded after the primary file and can override it; Staging calls this “configuration layering.” Running Staging with --printconf shows the exact path of its primary file on your system, and --editconf opens that file in your default text editor.
The one-minute version: Let DOSBox make the file (it does, on first run). On Windows, open it through Start Menu → DOSBox-0.74-3 → Options โ do not go hunting in Program Files, where the manual says the file will not work correctly. Edit only the value after the =, save, restart DOSBox. For a game that needs special settings, give it its own small file and start DOSBox with -conf pointing at it; anything that file leaves out comes from your global file.
Sources
DOSBox (dosbox.com) โ “DOSBox v0.74-3 Manual” โ Section 13 (the configuration file is created on first run; the Windows, Linux and Mac locations; sections and property=value lines; # and % comment lines; the -conf load order and the local dosbox.conf; the Vista/7 warning about Windows, Program Files and c:\), Section 4 (the CONFIG program: -writeconf, -set, -get, and its worked examples), and Section 12 (the Status Window). https://www.dosbox.com/DOSBoxManual.html
DOSBox Wiki โ “Dosbox.conf” โ the file works globally and/or locally per game with left-out settings taken from the global file; the Windows XP and Vista/7/8.x folder paths; the Status Window shows the location at startup; the DOSBox 0.74 Options.bat way of opening the file; the per-game conf file and shortcut recommendation. https://www.dosbox.com/wiki/Dosbox.conf
DOSBox Staging โ “Configuration” manual page โ the primary configuration (dosbox-staging.conf, its Windows path, automatic creation), local configurations and layering order, and the --printconf and --editconf options. Staging is a separate program; its paragraph is labelled as such on this page. https://www.dosbox-staging.org/0.83/manual/using-dosbox-staging/configuration/
Checked November 7, 2026
Related guides: Jazz Jackrabbit DOSBox Config, DOSBox Config for Warcraft, DOSBox Screenshots and Video Capture, DOSBox-X vs DOSBox and Running The Oregon Trail (DOS) on a Modern PC.