DOSBox Fullscreen Black Screen Fix — In Plain Words
output=surface, and PCGamingWiki’s documented fix for a green or black fullscreen is to change it to output=overlay — and if that does not do it, to keep trying the other output modes until one works. One warning travels with that fix: a GOG forum report describes overlay itself freezing a modern Windows 11 machine in fullscreen, where output=opengl was the setting that worked. Both positions are printed below, labeled — try them in order and keep the one your machine likes.
Honest labels, up front. Every setting on this page is a documented starting point copied from the public sources in the Sources box — including one place where two sources point in opposite directions, printed as exactly that. None of these settings has been tested by playing the game for this page: the DisBox settings collection this page belongs to holds 0 settings verified by actual play.
These settings live in 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.
What is happening
DOSBox draws its picture through a setting called output, in the [sdl] section of its configuration file. The DOSBox Wiki’s configuration page lists the choices — surface, overlay, opengl, openglnb, ddraw — and notes the catch with the default: surface does not support scaling or aspect correction. Windowed, that mostly shows up as a small picture. Fullscreen, on some video cards, it shows up as no picture at all: PCGamingWiki’s DOSBox page has a section for exactly this — “with some video cards, DOSBox’s default output mode will render with a green or black screen in fullscreen mode.”
Two key facts before you change anything: Alt+Enter switches between windowed and fullscreen at any time (that is the DOSBox manual’s own answer to “how do I change to fullscreen?”), so you can always get back to the window. And the manual’s advice when fullscreen “looks wrong” is to play with three options: fullresolution, output and aspect. This page walks them in that spirit.
Step 1: change the output setting
PCGamingWiki’s fix, in its own steps:
- Edit the DOSBox configuration file (
dosbox-0.74.conf,dosbox.conf, or similar — store editions give the file the game’s name). - Change
output=surfacetooutput=overlay. - Save your changes and run the game again.
- “If the problem persists, edit it again and try different modes until you get one that works.”
If your copy came from GOG, PCGamingWiki gives the same fix through GOG’s own tool instead of the file: run the game’s Graphic Mode Setup from the Start menu, change the graphic mode to “Overlay” or “DDraw”, choose Save Settings, and run the game again. It adds one honest warning about that tool: it “can be rather buggy: it may crash, freeze or simply not save changed settings when exiting” — so if the setting does not seem to stick, editing the file directly is the fallback.
Step 2: the disagreement — when overlay itself is the problem
One modern report points the other way, and this page prints it instead of smoothing it over. In a GOG forum thread about Zork Nemesis locking up on launch, a poster traces the freeze to “a combination of your output mode (output=overlay) and fullscreen settings clashing with modern Windows drivers inside that older version of DOSBox (0.74-2)”: overlay, they report, “frequently causes hard freezes and black-screen system hangs on modern GPUs and Windows 11 architectures.” Their fix for that machine:
output=opengl (or output=ddraw if opengl gives trouble) fullscreen=false (for the first launch) fullresolution=original
Start windowed, confirm the game boots, then press Alt+Enter to go fullscreen once it is running. So the two sources are not averaged here: PCGamingWiki says overlay is the fix for a black fullscreen; the GOG report says overlay caused the black screen on its Windows 11 machine and opengl fixed it. The working order that respects both: try overlay first; if fullscreen still fails — or the machine freezes — switch to opengl (then ddraw), and do the first test from a window. Whichever mode works on your video card is the right one; that is exactly what PCGamingWiki’s “try different modes until you get one that works” means in practice.
Step 3: the resolution line
The other fullscreen setting is fullresolution. The DOSBox Wiki explains what it does: it scales the application to that size if the output device supports hardware scaling — which is every output except surface. Its default is original, the game’s own resolution; if that is smaller than what your monitor and video card support, DOSBox switches to the closest match the drivers offer. The GOG report above recommends keeping fullresolution=original so the picture is not stretched or distorted. Leave it at original while you are fixing the black screen; changing two things at once hides which one worked.
Different problem: the picture is far too big
If fullscreen works but the picture is huge and spilling off the screen, that is a different fault with its own documented answer. The DOSBox manual’s FAQ “My fullscreen is too large” explains it can happen on Windows 10 when display scaling is set above 100% — Windows resizes the screen on top of DOSBox resizing it. Its fix is a Windows compatibility setting on the DOSBox shortcut: right-click the DOSBox icon, choose Properties, open the Compatibility tab, click “Change high DPI settings”, tick “Override high DPI scaling behaviour” and set it to “Application”. The manual notes that setting can make the windowed picture the wrong size instead, in which case you set windowresolution in the configuration file (its example is 1024x768) — or lower the fullresolution value.
Which DOSBox this page is about
These steps are written for DOSBox 0.74 and the store editions built on it, where the settings above live. DOSBox Staging is a separate, newer build with its own manual and some different setting names; if you run Staging, its own documentation is the matching source. (This site’s guide DOSBox Output: OpenGL vs Surface vs Overlay compares the output modes themselves, and DOSBox-X vs DOSBox explains how the builds differ.)
The one-minute version: Window fine, fullscreen black or green → edit the configuration file and change output=surface to output=overlay (PCGamingWiki’s fix). Still black, or the machine freezes on a modern Windows 11 setup → try output=opengl, then ddraw, starting windowed with fullscreen=false and pressing Alt+Enter once the game is running (the GOG report’s fix). Keep fullresolution=original while you test. Picture too big instead of black → the Windows high-DPI override in the manual’s “fullscreen is too large” answer.
Sources
PCGamingWiki — “DOSBox” — the “Green or black screen in fullscreen mode” section (change output=surface to output=overlay; try different modes until one works; the GOG Graphic Mode Setup route, Overlay or DDraw, with the warning that the tool can fail to save settings). https://www.pcgamingwiki.com/wiki/DOSBox
GOG.com forum — “Zork Nemesis DOSBox configuration (fix window size and scroll speed)” — one user’s report that output=overlay with fullscreen caused hard freezes and black-screen hangs on a modern GPU and Windows 11 with DOSBox 0.74-2, and the fix that worked there (output=opengl or ddraw, fullscreen=false for the first launch, fullresolution=original, Alt+Enter afterwards). Printed above as a single report, not a general rule. http://www.gog.com/forum/zork_series/zork_nemesis_dosbox_configuration_fix_window_size_and_scroll_speed
DOSBox Wiki — “Configuration:SDL” — the output values (surface, overlay, opengl, openglnb, ddraw), that surface does not support scaling or aspect correction, and what fullresolution does and defaults to. https://www.dosbox.com/wiki/Configuration:SDL
DOSBox (dosbox.com) — “DOSBox v0.74-3 Manual” — Alt+Enter for fullscreen, the “play with fullresolution, output and aspect” advice, and the “My fullscreen is too large” answer (Windows 10 display scaling above 100%; the high-DPI override steps; the windowresolution example). https://www.dosbox.com/DOSBoxManual.html
Checked November 7, 2026
Related guides: Lemmings Has No Sound in DOSBox? The Fix, Ultima VII in DOSBox and DOSBox Keyboard Types the Wrong Characters.