Magpie and DxWnd are another pair that sound interchangeable and are not: Magpie is a superb, free scaler for windows that already exist — DxWnd exists to create the window in the first place. If your classic game is trapped in exclusive fullscreen, Magpie cannot see it. If your classic game already runs in a small window that looks like soup on a 4K monitor, DxWnd’s job is done and Magpie’s begins. This page is part of our DxWnd alternatives comparison series.
What Magpie Does
Magpie, developed by Blinue and published as free, open-source software (GPL-3.0) on GitHub, is a window upscaler for Windows 10 and 11. It is actively maintained — release v0.13.0 shipped in October 2026, and the project has on the order of sixteen thousand GitHub stars. You run your game in a window, press Magpie’s hotkey, and Magpie captures the window and re-presents it filling your screen through a scaling algorithm of your choice: FSR, Anime4K for animated content, Lanczos, integer-style scaling for pixel art, CRT shader effects for period flavour, and a library of other filters. Everything is per-window and non-destructive: press the hotkey again and your ordinary window is back.
The quality on offer is real. For 2D and pixel-era games especially, the jump from a GPU’s naive bilinear stretch to integer or FSR scaling is the difference between mush and the image the artists actually drew. Magpie’s hint list even speaks directly to this audience — it advises setting the “High DPI scaling override” to “Application” in a game’s compatibility settings when an older title mishandles DPI scaling, a sign of how squarely it targets old games in windows.
Its requirements are modest and modern: Magpie’s own readme asks for Windows 10 version 1903 or later (or Windows 11) and a GPU with DirectX feature level 11 — hardware from roughly the last decade and a half. Nothing about it is period software; it is a current tool that happens to serve period games beautifully.
Where Magpie Stops
At the window’s edge. Magpie’s input is a window that Windows can capture, which means the game must already run windowed (or borderless) before Magpie has anything to upscale. A DirectDraw-era title that seizes the display, switches the desktop to 640×480 and draws through exclusive fullscreen gives Magpie nothing. And once a window exists, Magpie does not touch the game’s behaviour: no palette emulation for 256-colour titles, no timing correction, no locale, no input or CD fixes. It is a presentation tool of high quality and deliberately narrow scope. Our video settings guide covers the much plainer presentation options inside DxWnd itself — the contrast in ambition is the comparison in miniature.
Scaling Is Not Rendering — Setting Expectations
One clarification saves disappointment on both sides of this comparison. When Magpie upscales a 640×480 window to 3840×2160, the screen shows more pixels but the game still only ever produced 640×480 worth of information. A good scaler’s job is to spend those pixels wisely: integer scaling spends them as exact blocks, which is why pixel art looks carved rather than smeared, while FSR and Lanczos spend them on smooth, plausible edges, which suits early 3D. No scaler invents detail that the game did not draw — that is a different technology with different artefacts, and neither Magpie nor DxWnd claims it. The practical consequence: for a 2D classic, the combination “native-resolution window plus integer scaling” is effectively the best image the game can ever produce, and Magpie delivers it free. Expecting any tool in this toolbox to make a 1998 game look like a remaster is how remasters get sold.
Magpie’s capture model also explains its one recurring friction with older titles: it works through Windows’ graphics-capture facilities, so the game window must be a real, capturable window in good standing. Games that draw through unusual surfaces, or that fight the window manager — the exact population DxWnd’s troubleshooting pages exist for — may need their behaviour fixed first. Sequence, again: window health first, scaling second.
What DxWnd Does
DxWnd hooks fullscreen-era games at launch and forces them to render inside a standard window, with the period compatibility layer — palettes, timing, locale, virtual CD, registry — wrapped around the result. Its built-in scaling is the weakest part of the package: it stretches, correctly but unremarkably. That is precisely the gap Magpie fills, which is why the honest comparison here is not “which is better” but “which half of the job is yours.” The standard workflow in our guide to using DxWnd gets a title like SimGolf into its window; Magpie is then the best free way to make that window look like it belongs on a modern display.
| Question | Magpie | DxWnd |
|---|---|---|
| Primary layer | Window image scaling (post-capture) | Launch-time hooking + compatibility |
| Needs a windowed mode first? | Yes — it upscales existing windows | No — creating the window is its purpose |
| Scaling algorithms | FSR, Anime4K, Lanczos, integer-style, CRT effects and more | Basic stretch |
| Palette / timing / locale / CD fixes | No | Yes |
| Maintenance | Active (v0.13.0, Oct 2026) | Active (v2.06.16, Oct 2026) |
| Price | Free, open-source (GPL-3.0) | Free and open-source |
One More Asymmetry: Magpie Scales Anything
Magpie’s own repository describes it as a general-purpose window upscaler, and the generality is real: emulators, elderly utilities with postage-stamp interfaces, media players, a browser window you want on the TV — if it is a window, Magpie will scale it, games or not. DxWnd has the opposite temperament: it is indifferent to windows in general and cares only about the narrow class of programs that refuse to become one. If your scaling needs extend beyond fullscreen-era games, Magpie earns its place in your toolbox on its own merits, with DxWnd as the specialist you call for the titles Magpie cannot reach. Neither tool’s author would dispute the division.
The Two-Tool Stack
Chaining them is painless because they never compete for the same job: DxWnd’s profile puts the game in a window at its native resolution; Magpie’s hotkey takes that window fullscreen with good scaling. There is no DLL conflict and nothing to configure in either tool about the other. If your game is 3D and also runs at an unhappy frame rate, the frame-generation side of the toolbox is a different tool again — see DxWnd vs Lossless Scaling — but for pure scaling quality at zero cost, Magpie is the first thing to try.
The Verdict
| Choose… | If… |
|---|---|
| Magpie | Your game already runs in a window and your complaint is purely visual — blur, mushy pixels, a tiny window on a big monitor. It is free, current, and excellent at exactly this. |
| DxWnd | Your game will not run in a window at all, or needs the era’s compatibility fixes. Window it first with the current DxWnd build — then hand the window to Magpie and enjoy both. Tested per-game starting points live in our games hub. |