Slay the Spire 2 runs on Godot 4's Vulkan renderer and represents one of the lightest GPU workloads in the TargetFPS catalogue. The game is a 2D-style card-based roguelike with hand-crafted illustrated art, animated card effects, and relatively static scene composition — the engine is never pushing millions of triangles or complex lighting calculations. VRAM demand tops out at 2 GB even at 4K, reflecting the modest texture atlas sizes used for cards, relics, and encounter backdrops. Nearly any discrete GPU from the last decade will run this at uncapped framerates. Optimization headroom is excellent: the Vulkan backend in Godot 4 handles draw call batching efficiently, and the engine's relatively simple render graph means per-frame GPU time is low. The only meaningful performance levers are shadow computation, anti-aliasing resolve cost, and particle effect overdraw during combat animations. Integrated graphics and low-power laptops are fully viable targets.
Below is a per-setting breakdown: what each option does, how much it costs, and the value we recommend — tuned to keep the image looking right while reclaiming frames. Want the exact numbers for your GPU? Open the optimizer →
Recommended settings for Slay the Spire 2
Reference rig: RTX 4080 at 1440p, balanced preset. Values are accurate to Slay the Spire 2's in-game options.
Texture Quality
High
Low cost
Typical impact 0-5% · 2% fps cost
In Slay the Spire 2, we recommend Texture Quality at High (2% fps cost).
Controls the maximum mipmap resolution loaded for surface textures. Higher levels stream larger texture maps (2K/4K) from disk into VRAM via the texture streaming pool. The GPU samples these during fragment shading using the currently bound sampler state. The FPS cost is minimal when VRAM is sufficient because texture fetch latency is hidden by the cache hierarchy, but exceeding VRAM capacity triggers page-faulting and hitching as textures are swapped between system RAM and VRAM.
In Slay the Spire 2: Governs the mipmap resolution loaded for card art, character illustrations, enemy sprites, and encounter background paintings in Godot 4's texture streaming system. Because Slay the Spire 2 uses pre-rendered 2D-style assets rather than tiling PBR surfaces, the texture pool is small — the jump from Low to High increases VRAM usage by roughly 0.5–1 GB but has near-zero impact on frame time since the GPU is never texture-bandwidth constrained at this asset density. Only relevant on systems with less than 2 GB VRAM.
Shadow Quality
High
Low cost
Typical impact 8-25% · 4% fps cost
In Slay the Spire 2, we recommend Shadow Quality at High (4% fps cost).
Controls shadow map resolution, filtering method, and cascade count for dynamic shadows. The engine renders the scene from each light source perspective into depth-only shadow map textures. Higher settings increase shadow map resolution (1024 to 4096 texels), add more cascaded shadow map splits for the directional light (improving near-field resolution), and enable softer PCF or PCSS filtering which requires more depth comparison samples per pixel during the lighting pass.
In Slay the Spire 2: Controls whether Godot 4's shadow map pipeline is active and at what resolution it renders depth passes for encounter scene lighting. At Off, no shadow map render passes are dispatched at all — the largest single saving available in this title. Low uses a 512-texel map; High steps up to 2048. Because encounter backgrounds are largely static illustrations, the visual difference between Off and Low is subtle, but the frame-time saving on Off is disproportionately large relative to the game's otherwise minimal GPU load.
Anti-Aliasing
MSAA 2x
Low cost
Typical impact 2-15% · 3% fps cost
In Slay the Spire 2, we recommend Anti-Aliasing at MSAA 2x (3% fps cost).
Smooths jagged edges (aliasing) on geometric boundaries. FXAA is a single-pass edge-detection blur — cheap but softens the image. TAA accumulates multiple frames using motion vectors, sampling sub-pixel jitter offsets to reconstruct smoother edges — moderate cost with potential ghosting. SMAA uses pattern-matching edge detection with a more intelligent blend. MSAA runs the rasterizer at 2x/4x the sample count, evaluating coverage for each triangle edge — expensive because it multiplies ROP work and render target memory, but produces sharp geometry edges without blur.
In Slay the Spire 2: Selects the edge-smoothing method applied to Godot 4's final composited frame. Off incurs no cost and is acceptable given the painterly art style where sub-pixel geometry aliasing is barely perceptible. FXAA runs a single-pass edge-detection blur in the post-process stack — negligible cost but softens fine card text slightly. MSAA 2x runs the rasterizer at double sample density, which is clean but wasteful for a 2D-dominated scene where geometric edges are sparse; the ROP cost is real even if the absolute numbers are small on this GPU-light title.
Effect Quality
High
Low cost
Typical impact 3-15% · 2% fps cost
In Slay the Spire 2, we recommend Effect Quality at High (2% fps cost).
Controls the visual fidelity of gameplay effects including explosions, weapon impacts, ability VFX, and environmental interactions. Higher settings increase particle emitter counts per effect, use higher-resolution flipbook or mesh particles instead of simple sprites, enable GPU particle simulation via compute shaders, and add dynamic lighting from effects (each explosion spawning a temporary point light). The cost is highly variable — intense combat with multiple overlapping effects can produce 4-8x overdraw from layered transparent particles.
In Slay the Spire 2: Determines particle emitter count, flipbook texture resolution, and overdraw budget for card play animations — the screen-filling energy blasts, status effect bursts, and relic activation sparks that fire during combat. High spawns more billboard particles per effect with larger emitter radii, increasing overdraw in the transparent composite pass. Low halves particle count and uses smaller sprites. In multi-card combo turns where several effects overlap simultaneously, High can briefly spike frame time on integrated graphics; Low keeps the overdraw budget flat throughout even the busiest turns.
V-Sync
On
Low cost
Typical impact 0% · no measurable cost
In Slay the Spire 2, we recommend V-Sync at On (no measurable cost).
Synchronizes the GPU's framebuffer swap with the monitor's vertical blanking interval to prevent screen tearing. When enabled, the GPU holds the completed frame until the monitor signals it is ready. If the GPU cannot maintain the refresh rate, VSync forces the frame to wait for the next blanking interval, causing framerate to drop to a fraction (e.g., 60fps to 30fps on a 60Hz display). This introduces up to one full frame of input latency. Triple buffering mitigates the fractional drop but adds more latency.
In Slay the Spire 2: When enabled, Godot 4 holds each completed frame until the display's vertical blanking interval, preventing tearing on the largely static encounter screens. Because Slay the Spire 2 renders well under a millisecond of GPU work per frame on most hardware, VSync's fractional framerate penalty (dropping from 144 to 72 fps if a frame is slightly late) is the only meaningful downside. On 60 Hz displays there is effectively no cost. Disable if you want uncapped frame output for minimum input latency during rapid deck-building menu navigation.