DOSBox Scalers and Aspect Correction, in Plain Words
[render] section of your DOSBox config file shape the picture. scaler (default normal2x) enlarges the game’s small picture and can smooth it. aspect (default false โ off) fixes the shape: many DOS games were drawn for a 4:3 screen using non-square pixels, so without aspect correction they look squashed or stretched. One gate controls both: the Wiki warns that the surface output “does not support scaling or aspect correction” โ with output=surface, neither setting does anything.
Honest labels, up front. Everything on this page is copied from the DOSBox Wiki, the configuration file DOSBox itself writes out, and โ in one clearly marked section โ the DOSBox Staging manual, which describes a different program with a different system (shaders instead of scalers) 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.
Aspect correction: the shape setting
The DOSBox Wiki’s dosbox.conf page defines the setting in one sentence: aspect means “Do aspect correction. It only affects non-square pixel modes like VGA Mode 13h, which has a resolution of 320x200 pixels and is used by many DOS games (DOOM, etc).” The reason it exists: those games “were designed for 4:3 displays, and without aspect correction will look distorted and not as the developer intended.” The default is false โ correction is off until you turn it on:
[render] aspect=true
The configuration file DOSBox writes out adds a practical hint in its fullscreen comments: “Using your monitor’s native resolution with aspect=true might give the best results.” The same file’s [render] comment attaches a cost to be aware of: “Do aspect correction, if your output method doesn’t support scaling this can slow things down!”
Scalers: the size-and-smoothness setting
The Wiki: the scaler “is used to enlarge and enhance low resolution modes, BEFORE any additional scaling done according to the Fullresolution and Windowresolution settings under [sdl]” โ so the scaler is the first enlargement, and the window/fullscreen size settings work on its result. The full value list is none, normal2x, normal3x, tv2x, tv3x, rgb2x, rgb3x, scan2x, scan3x, advmame2x, advmame3x, advinterp2x, advinterp3x, 2xsai, super2xsai, supereagle, hq2x, hq3x, and the default is normal2x. The Wiki describes the families:
- none โ “no scaling is performed.”
- normal โ “nearest-neighbour scaling (big square pixels).”
- scan โ “like ‘normal’, but with horizontal black lines.”
- tv โ “like ‘scan’, but with darkened versions of the data instead of black lines.”
- rgb โ “simulates the phosphors on a dot trio CRT.”
- advmame โ “smooths corners and removes jaggies from diagonal lines”; advinterp is “identical to ‘advmame’.”
- sai โ “similar to ‘advmame’ but with much softer color gradients and edges”; supersai is “similar to ‘sai’ but sharper.”
- hq โ “a ‘high quality’ scaler which delivers a cleaner and sharper image than ‘advmame’ or ‘sai’ scalers.”
The number after the name is the enlargement: 2x doubles the picture, 3x triples it. The configuration file’s own comment adds one option the Wiki’s list does not spell out: “If ‘forced’ is appended, then the scaler will be used even if the result might not be desired” โ as in scaler=normal2x forced.
The gate: your output setting decides whether any of this works
Both settings pass through the [sdl] section’s output line. The Wiki’s output entry says it flatly: “Surface does not support scaling or aspect correction.” The configuration file says the same thing from the other side, in its window-resolution comment: “Scale the window to this size IF the output device supports hardware scaling. (output=surface does not!)” So if you set a scaler or aspect=true and nothing changes, check the output line first โ choosing which output mode to use is a separate question, covered in this collection’s output guide; this page is about the two [render] settings themselves.
The third [render] line, for completeness: frameskip โ “How many frames DOSBox skips before drawing one” (default 0). It is a speed trade-off, not a picture-shape setting; the manual’s speed section treats skipped frames as fluidity traded for speed.
If you run DOSBox Staging instead
DOSBox Staging is a separate program, and it replaced the scaler list with GPU shaders โ do not look for scaler= values from the list above in its manual. Staging’s picture is set by a shader line in [render]. Its default is crt-auto, an adaptive CRT shader that changes its monitor emulation to match what the game is producing (a VGA game gets a VGA-monitor look, an EGA or CGA game a thicker-scanline one); the shaders page notes these shaders generally need at least three times the video mode’s vertical resolution to produce the intended effect, and fall back to the sharp shader when the window is too small. If you want the plain, crisp look instead: “If you prefer a crisp ‘sharp pixel’ look without any CRT emulation, set shader to sharp” โ Staging describes sharp as upscaling “treating the pixels as small rectangles, resulting in a sharp image with minimum blur while maintaining the correct pixel aspect ratio,” which is where Staging handles the shape question this page’s aspect setting answers in 0.74. Some familiar names survive as bundled shaders (the page lists scaler shaders such as advinterp2x, advmame2x and the xbr family), but they are shaders chosen through the shader setting โ Staging’s system, labelled as such, not a continuation of the 0.74 list.
The one-minute version: Characters look fat or squashed in a 320x200 game? Set aspect=true. Picture too small or too jagged? Pick a scaler โ normal2x (the default) for honest square pixels, an advmame/hq family scaler for smoothing. Nothing changing at all? Your output is probably surface, which supports neither scaling nor aspect correction.
Sources
DOSBox Wiki โ “Dosbox.conf” โ the [render] section (frameskip’s definition and default; aspect’s definition, the Mode 13h / DOOM example, the 4:3 developer-intent reasoning, default false; the scaler’s full value list, its position before the [sdl] resolution scaling, the family descriptions, default normal2x) and the [sdl] section (output’s values and “Surface does not support scaling or aspect correction”). https://www.dosbox.com/wiki/Dosbox.conf
The configuration file DOSBox 0.74 writes out โ its own comments: fullresolution (“Using your monitor’s native resolution with aspect=true might give the best results”), windowresolution (“output=surface does not!”), and [render] (aspect’s slow-down caution; the scaler’s “forced” suffix). Read in full; two printings of the shipped file agree on these sections.
DOSBox Staging โ “Shaders” manual page โ the labelled Staging section: shaders instead of a scaler list, the crt-auto default and its adaptive behaviour, the three-times-vertical-resolution guidance and the sharp fallback, the sharp shader’s description, and the bundled scaler-style shaders. Staging is a separate program; its paragraph is labelled as such on this page. https://www.dosbox-staging.org/0.83/manual/graphics/rendering/shaders/
Checked November 7, 2026
Related guides: DOSBox Config for Warcraft, What Is the Z, DOSBox CPU Core and DOSBox Cycles for DOOM and DOOM II.