DxWnd and Lossless Scaling are usually described as rivals, but they barely overlap: Lossless Scaling polishes a game that is already running in a window, and DxWnd’s entire job is creating that window for games that refuse to have one. Many retro players end up running both, in that order. This comparison explains what each tool really does, where each one stops, and when one of them alone is enough. It is part of our DxWnd alternatives comparison series.
What Lossless Scaling Does
Lossless Scaling, by THS, is sold on Steam for $6.99 (checked October 2026) and has been in active development since 2018. It works on whatever a window is already showing, in two ways. First, scaling: it enlarges the window’s image to fill your screen using a choice of algorithms — its own LS1, AMD’s FSR, NVIDIA Image Scaling, integer scaling for pixel-perfect retro graphics, and others such as xBR and Anime4K. Second, LSFG frame generation: it analyses the moving image and inserts generated frames between the real ones, so a game rendering at 30 frames per second can be displayed at 60 or beyond.
Both talents come with a hard precondition, stated plainly in its documentation and every honest review: the game must be running in a windowed or borderless mode. Lossless Scaling does not negotiate with a game that seizes the display — it has nothing to capture. Frame generation also has physics it cannot repeal: generated frames are interpolated guesses, so a low or unstable base frame rate produces visible artefacts and added input latency. It multiplies motion; it does not repair the game producing it.
What DxWnd Does — and Doesn’t
DxWnd hooks a game at launch and forces exclusive-fullscreen titles — overwhelmingly the DirectDraw and early-DirectX generation — to render inside an ordinary window, with per-game compatibility emulation around it: palette handling, timing control, locale, CD behaviour. The window geometry side is covered in our window size and position guide, and the video presentation options in our video settings guide.
What DxWnd conspicuously lacks is everything Lossless Scaling is for. Its built-in scaling is functional, not beautiful — a 640×480 game stretched to a 4K desktop by DxWnd alone is soft, and on an integer-multiple display it still will not give you the crisp, exact pixels an integer scaler produces. It has no frame generation at all: if the game runs at 30 fps, DxWnd shows you 30 honest frames. Judged purely as a picture-quality tool, DxWnd loses this comparison, and it is not close. Judged as a compatibility tool, Lossless Scaling never enters the contest — it assumes the compatibility problem is already solved.
What Frame Generation Cannot Do for Old Games
Because LSFG works on the captured image rather than inside the game, everything in the frame is interpolated together — the 3D scene, but also the HUD, menus and cursor. On modern games with high base frame rates that trade is usually worth it. On legacy titles, three cautions from the mechanism itself apply. First, the base rate rules: frame generation interpolating a stuttering 18 fps does not produce smooth 36; it produces smoother-looking stutter, and the underlying game logic still advances in the original uneven steps. Second, latency is additive: capturing, analysing and generating frames costs time, which a twitch game will make you feel — the community guidance around the tool consistently steers competitive players away from it. Third, it needs GPU headroom: the game and LSFG share one graphics card, and on integrated graphics the realistic feature is the scaling half, not generation. None of this is a defect in the tool; it is what “post-capture processing” means. It is also why frame generation can never substitute for fixing a game whose timing is broken at the source — that fix lives at DxWnd’s layer.
The Stack: Why They Pair So Well
The classic retro setup uses the tools in sequence. DxWnd does the archaeology: the 1999 game is hooked, windowed at its native 640×480 or 800×600, its palette and timing behaviours emulated. Then Lossless Scaling takes that small window and presents it properly: integer scaling turns each original pixel into an exact block of modern pixels — the single biggest visual upgrade available for pixel-era games — or LS1/FSR smooths a 3D title, and LSFG can smooth motion on top if the base frame rate is stable. Each tool is doing the half the other cannot. Timing problems belong to DxWnd’s layer specifically; our game-runs-too-fast guide shows the symptom, because no amount of frame generation fixes a game whose internal clock is broken — it just interpolates the breakage at a higher frame rate.
| Question | Lossless Scaling | DxWnd |
|---|---|---|
| Primary layer | Image presentation (post-capture) | Launch-time hooking + compatibility |
| Needs a windowed mode first? | Yes — windowed or borderless is a requirement | No — creating the window is its purpose |
| Upscaling quality | Its specialty: LS1, FSR, NIS, integer and more | Basic stretch only |
| Frame generation | Yes (LSFG) | No |
| Palette / timing / locale / CD fixes | No | Yes |
| Price | $6.99 on Steam (Oct 2026) | Free and open-source |
A Note on Platforms
Lossless Scaling’s full feature set is a Windows application; its frame generation has also reached SteamOS, Linux and the Steam Deck through community-developed integrations, which is where much of its current fame lives — handheld players smoothing out games that never shipped with frame generation. DxWnd is Windows-only, full stop: it hooks Win32 programs, and the classics it serves are Win32 programs. If your retro library lives on a Deck, the window-creation half of this comparison is a different conversation (Wine and Proton handle that layer there); if it lives on a Windows desktop, this page’s division of labour applies as written.
When One Tool Is Enough
If your game already windows happily and your only complaints are “blurry” and “choppy,” DxWnd adds nothing — buy Lossless Scaling and stop. If your game will not window at all, Lossless Scaling cannot even see it — start with DxWnd via our step-by-step guide, and consider Lossless Scaling afterwards, purely as the presentation upgrade. And if your game is a modern title with native borderless and native upscaling, honestly, you may need neither.
The Verdict
| Choose… | If… |
|---|---|
| Lossless Scaling | Your game already runs in a window and you want sharper upscaling — integer scaling for pixel art above all — or smoother motion via frame generation. |
| DxWnd | Your game is a fullscreen-only classic that nothing else can window, or it needs era compatibility fixes. Take the window from the current DxWnd build first — then, if you like, let Lossless Scaling finish the picture. Per-game starting points are in our games hub. |