Factorio: Best config.ini for High-Resolution Sprite Caching

The objective is to enable On-Disk Caching of the pre-processed sprite atlases. By default, Factorio “re-stitches” thousands of individual PNGs into large atlases ($A_{size}$) every time it launches; our config bypasses this by saving the finished result to your SSD.

File Path & Setup

1. Locate the file: %AppData%\Factorio\config\config.ini
2. Hidden Menu Alternative: You can also access these by holding Ctrl + Alt and clicking Settings in the main menu. A secret button labeled “The Rest” will appear.
3. VRAM Check: High-resolution sprites in 2026 require at least 4GB of VRAM. If you have an 8GB+ card, ensure video-memory-usage is set to all.

Optimized “Instant-Launch” Configuration Table

Parameter	Recommended Value	Technical Purpose
cache-sprite-atlas	true	The Master Fix. Saves processed atlases to disk for instant loading.
compress-sprite-atlas-cache	true	Reduces cache size by ~70% (Essential for large modpacks).
cache-sprite-atlas-count	2	Keeps caches for two different mod-sets simultaneously.
video-memory-usage	all	Allows the GPU to hold the entire HD sprite library in VRAM.
max-texture-size	0 (Auto)	Let the engine determine the largest power-of-two size for your GPU.

[graphics]
graphics-quality=high
video-memory-usage=all
max-texture-size=0
cache-sprite-atlas=true
compress-sprite-atlas-cache=true
cache-sprite-atlas-count=2
texture-compression=true
gpu-accelerated-compression=true
gpu-accelerated-mipmap-compression=true

[other]
cache-prototype-data=true

HowTo: Engineering the Ultimate Sprite Pipeline

Follow these GameEngineer.net technical steps to eliminate “Sprite Stutter”:

1. The First Run Penalty: When you first enable cache-sprite-atlas, your next launch will be slower than usual. Factorio is “baking” the cache files to your drive. Every subsequent launch will be up to 10x faster until you update the game or change your mods.
2. GPU-Accelerated Compression: In 2026, modern GPUs handle BC7/DXT compression much faster than the CPU. Ensure gpu-accelerated-compression=true is active to speed up the initial cache generation phase.
3. Prototype Caching: Under the [other] section, cache-prototype-data=true works similarly but for the game’s logic and item definitions. This reduces the “Building Prototypes” loading bar, which is highly beneficial for megabases with hundreds of custom entities.
4. Managing Atlas Size: If you experience flickering or “missing” sprites on high-resolution settings, your GPU might struggle with 16k textures. Change max-texture-size to 8192 to force the engine into using more, but smaller, memory blocks.
5. Linear Magnification: For the sharpest visuals at high zoom levels, set force-linear-magnification=true. This avoids the “pixelated” look on curved pipes and inserter legs, using the original high-fidelity renders from the developers.

Technical Explanation: Atlas Stitching and I/O Throughput

Factorio uses a custom engine designed for massive 2D throughput. The “Loading Sprites” phase is actually a Bin-Packing problem ($P_{pack}$). The engine takes individual sprites ($s_1, s_2, … s_n$) and arranges them into massive “atlases” to minimize Draw Call overhead ($D_{call}$).

By enabling cache-sprite-atlas, you move this computation from a runtime CPU task to a static I/O read. In 2026, reading a 1GB pre-compiled atlas from an NVMe SSD ($V_{read} \approx 5000\text{MB/s}$) is exponentially faster than recalculating the optimal spatial arrangement of 10,000 sprites on every boot. This ensures your Graphics Thread ($T_{gfx}$) is fully populated with assets before the game world even initializes.