Deskrawl Memory Usage and FPS: What the 130MB Fix Actually Means

One official performance number exists for this game: patch 1.0.0g removed about 130 MB of RAM consumption on 29 September 2026, and the developers never published a baseline, a peak, or a frame rate. The two official numbers that do exist sit on the store page and disagree by 4× — 4 GB RAM minimum, 16 GB RAM recommended. Everything below is read out of the shipped build or posted by a player, and each line says which.

What the 130 MB line says, and what it leaves out

Official source: Patch 1.0.0g — Various Improvements and Fixes, 29 September 2026

The bullet, verbatim: "Reduced RAM consumption by about 130 MB (more RAM improvements coming in next patches)." Note the hedge — "about" — and the promise at the end. As of 30 September 2026 that is still the newest announcement, so the follow-up work has not landed; the patch archive is worth re-checking.

Any page claiming Deskrawl "uses 1.5 GB" quotes a player.

The two official RAM numbers disagree by 4×

Read from the Steam store API on 1 October 2026 (appdetails?appids=4623570&l=english&cc=us, field data.pc_requirements); the Chinese store page carries the same pair.

Most games spread two to three times between tiers. This one spreads 4× on RAM while the GPU jumps a single 2013-era generation: a small window of sprites costs nothing on the GPU, but a browser, an editor and a video call run underneath it for eight hours. If you play on 8 GB, the 4 GB minimum says nothing about whether 130 MB hurts — the saving is real, the baseline is not.

This is a resident game, not a peak-performance game

The premise is a transparent panel parked at the bottom of your screen: a long-lived process competing with your browser, not a session with a loading screen.

Five window and stability fixes before launch day, then one memory line after. The record is thin for a reason: the build ships a performance-test harness and zero results. PerformanceTestRunInfo and PerformanceTestRunSettings in the shipped resources.assets both hold 0 rows, while the RunInfo schema names the fields that would settle this — ScreenWidth, ScreenRefreshRate, Vsync, AntiAliasing, GraphicsApi, SystemMemorySizeMB, GraphicsDeviceName. The tooling exists; the numbers were never captured.

What "Extremely Low" actually switches off

The lowest preset is not called "Low". The interface table ships UI.Quality.Low labelled "Extremely Low" — which is why hunting for a "Low" option finds nothing. The engine tiers in QualitySettings.asset are Very Low, Medium and Ultra. Read from the 1.0 launch build assets (2026-09-28); 1.0.0g touched none of them.

The Very Low tier is the only one that drops the ScreenSpaceAmbientOcclusion renderer feature — the default Renderer3D asset lists three features (decal, SSAO, transparent-window clear), Renderer3D_LowQuality lists two. And render scale is 1.0 on every tier, so there is no internal-resolution lever at all.

The settings panel, and the one key that matters most

SettingsPanelUI wires up seven sliders (master, music, SFX, game width, brightness, UI scale, HUD scale), four dropdowns (language, resolution, quality, frame rate), three toggles (fullscreen, always on top, background audio) and a button row. There is no V-Sync switch, no shadow slider, no render-scale slider and no density control.

The control that matters for a background game is the Boss Key, defaulted to Alt+B in patch 0.1.9 and rebindable since 0.1.12a. The game's own tooltip string, UI.BossKey.Hint: "Press {0} to instantly hide the window and mute audio. Press again to restore. Works even while the window is unfocused." One keystroke and the process goes dark and silent while farming continues. The width slider, declared [Range(0.5f, 1f)], takes the window to half width.

What players actually measured

Community-reported, not official, and the only RAM telemetry that exists. The original post is in Traditional Chinese; readings as posted.

Official source: Steam discussion, thread id 592942834747724407

The poster never names which update caused the jump. Two things are worth taking: the growth continued after startup, climbing further once a run was in progress — resident-process behaviour, not a one-off allocation; and the reinstall fix points at stale local data.

When it crashes, one dump says where

In a separate thread a player analyses their own crash.dmp, having fed it to an AI. It is community analysis of a player-supplied file — the developer has published nothing on crashes — but the shape is specific: exception 0xC0000005 ACCESS_VIOLATION, a null-pointer read at D3D12Core.dll + 0x1B4EBA, while Loading.AsyncRead and AssetGarbageCollectorHelper ran with several Job.Worker threads. The module list names UnityPlayer.dll (37 MB) and GameAssembly.dll (68 MB), matching the shipped Unity 6000.3.6f1 IL2CPP Windows build.

Official source: Steam discussion, thread id 594068631729518999

That reads as a render-resource lifetime race inside async asset load/unload, not memory exhaustion. The next poster in the PC-crash thread puts it differently: "it doesn't even consume much resources so there's likely something in your PC that's making it crash." A crash that takes the machine down is a different problem from a heavy one — check Event Viewer.

Multi-monitor is the most-reported "lag" complaint

What players call lag is often a resolution bug: with two screens, "the only available resolutions are those of the smaller screen" (thread), and one player's window stayed on the old display after a monitor change, bottom buttons unreachable.

A low-spec checklist

What you will not find in that menu: enemy density, shadow distance, render scale, or a memory cap. If the process must cost less than this, closing it is the real lever — offline earnings covers the cost, and Steam Deck has the Proton setup.

FAQ

How much RAM does Deskrawl use? Officially not published. Patch 1.0.0g removed about 130 MB with no baseline. The only official guidance is the store pair: 4 GB minimum, 16 GB recommended.

Is Deskrawl optimized? Directionally, and it says so — the 1.0.0g bullet ends "(more RAM improvements coming in next patches)". That is a promise, not a delivery.

Will running it all day cost me my save? Save-loss reports are a separate issue: Deskrawl Save File and Disappearing Items. Patch 0.1.10 raised auto-save reliability "to avoid lose all progress when game crashes".

Does it need a good GPU? Minimum is a GeForce GT 730 or Radeon R7 240, both 2013–2014 entry cards; recommended moves one generation to a GTX 660 / R9 270.

Why did my memory jump after an update? One player reported 650 MB going to 2100 MB after an unnamed update; a reply said a reinstall fixed it. Unconfirmed officially, but the cheapest thing to try.

Does low FPS stop the farming? Simulation runs on a fixed 0.02 second timestep in TimeManager.asset — 50 ticks per second regardless of frame rate — so low FPS is cosmetic, not lost progress.

Related Guides

• Deskrawl Release Date, Price and System Requirements — the rest of the hardware picture.
• Deskrawl Patch Notes: Every Official Update — when the promised memory work lands.
• Deskrawl Offline Earnings: The 8-Hour Cap — the alternative to leaving it resident.
• Deskrawl Save File and Disappearing Items — what a crash costs.