Roughly plan how much disk space you need for save files, plus optional DLC, screenshots/captures, and mod folders. Multiply the saves you keep by an average size, add extras, and get MB/GB totals with a copyable TSV summary. All of it is typed math in your browser — nothing is read from your PC and nothing is uploaded to DroidXP, the same local-only posture as APK Analyzer and APK String Extractor.
Save data ≈ slots × average MB per save. Slot count means how many rolls/checkpoints you keep at once (manual + autosave reserve). Sizes use MB based on
1024 KB (simple binary units like many OS folder summaries).
Leave blank for 0. Add rough sizes for content that often sits next to the title: DLC packs (GB), screenshots/video captures (MB), mod loadouts (GB). Base install size is not implied — check the store page or your library if you need that line item separately.
For cross-unit work see File Size Converter. Related gaming tools: Mouse DPI Calculator, Screen Resolution Checker.
Save folders, cloud quotas, and SSD upgrades are easier to reason about with a ballpark byte count. This page never touches your filesystem — you supply counts and sizes, and it adds them the same way APK Analyzer stays inside the browser for unpacking: no uploads, just transparent arithmetic.
slots × avg MB per save × 1024² bytes.Peek at the folder size in Windows/macOS/Linux for your title after a representative play session, or check a community wiki. Some games balloon after patches; others compress saves. Prefer a slightly high average if you rotate few slots but heavy autosaves run in the background.
Inputs may be stored in localStorage only on your device for convenience (same tab origin). They are not transmitted to DroidXP — comparable to pasting text into APK String Extractor without sending it anywhere.
No. You type planning numbers only — nothing is read from disk and nothing is uploaded, same local-only model as APK Analyzer and APK String Extractor.
No. Save sizes vary by title, patch, and mods. Use recent figures from your OS or backup tool when possible; this page is for rough capacity planning.
Check your save folder properties after playing a while, or search community wiki/PCGW for typical sizes — then divide manually or enter a conservative upper bound.
They grow for different reasons. Splitting lines helps you see whether cloud-sync limits, screenshots, or modpacks are the real space hog.
Not by default — add install size yourself if you want a “everything on disk” picture using the optional fields or a separate note. Store pages list download sizes.
If you enter the same byte totals, you can compare against vendor cloud caps — but each platform rounds and compresses differently; treat as a ballpark.
Yes. Use a dot as the decimal separator for average save size and other fields.
Yes. Rotating saves lowers steady-state needs; keep margin for autosaves and crash backups some games create alongside manual slots.
Yes — inputs stay in your browser tab; only normal page assets load from DroidXP.
Yes. OS updates, patches, and shader caches need headroom — many guides suggest keeping tens of gigabytes free on the system drive.