--- title: "Minecraft modpack hosting: sizing RAM and disk" description: "How to size a Forge, Fabric or NeoForge modpack server: read the author RAM requirement, work out world and backup disk, install from CurseForge." url: "https://streethosting.com.br/en/minecraft-modpack" type: "page" language: "en-US" --- Sized by the pack # Minecraft modpack hosting sized by the pack you actually run The right step comes out of three numbers: the memory left over with a full room, the size of the directory after the first week, and how many backups you keep. [See RAM and disk on every step](https://streethosting.com.br/en/minecraft-pro#plans) [Work out my pack RAM](https://streethosting.com.br/en/guides/minecraft/how-much-ram-does-a-minecraft-modpack-need) * São Paulo, Brazil * Anti-DDoS up to 400 Tbps * NVMe Quick answer The RAM published on the modpack page is the minimum for playing alone on the client, not for a server with people online. Take that as the floor, add headroom per concurrent player and check the disk: on a large pack the NVMe of the entry plan runs out before the memory does. ## The number on the pack page is the client one, not the server one The author memory recommendation was measured on the client, with one person playing, and a good share of it goes to rendering, texture atlases and mods that live on the player side. None of that loads on the server. Something else takes its place: every player keeps their own chunk radius loaded, and everything inside it is processed on every tick. A pack that fits in 6 GB for one person goes past that with six players in different corners, because that is six active regions instead of one. ## CurseForge and Modrinth ask for different paths On CurseForge the file that matters is the server pack, published in the files tab next to the client version. Without it you are left assembling the server from the client zip and cleaning by hand: shaders, minimap and interface mods break the boot. On Modrinth the format is the .mrpack, an index of mods with hashes, resolved by mrpack-install or packwiz. Either way, open the startup script before the first boot: on Forge and NeoForge the memory lives in user\_jvm\_args.txt, and the author value rarely matches the step you bought. ## On a large pack the disk runs out before the memory Four things grow for different reasons: the mods folder, fixed once installed; the world, which grows with exploration; the logs, with operating time; and the backups, with the retention you choose. Only the first is predictable on signup day. Every dimension the pack adds writes its own set of region files, so an exploration pack multiplies the map without anyone having explored much of the main world. Generating the map ahead of time avoids stutter in real time, but it charges the space all at once. ## Updating the pack with a world already generated has a cost When the new version removes or renames mods, the blocks from that mod stay written into the chunks already visited. The loader warns that there are missing registries and asks for a confirmation that deletes those blocks, which can mean an entire base turning into air. Take the full copy and test the upgrade on a separate instance with the world copied over: plans from 8 GB up include one subdivision, so it costs nothing extra. If it really does break, you can preserve the main world and reset only the mining dimension. Infrastructure ## What changes when sizing follows the pack * Disk proportional to memory across the whole ladder, from 30 GB NVMe on the 4 GB step to 480 GB on the 64 GB one. * CPU allocation that grows alongside, from 300% on the 4 GB plan to 900% on the 16 GB one. Use cases ## When this page solves your case * An automation pack, with machines processing even when nobody is online. * An exploration pack with its own dimensions, where the map grows before the memory does. * A server that has to validate a new pack version without risking the season. Optimization ## Adjustments that pay off on a modpack * Xmx in the pack script aligned with the ceiling of the step you bought. * View distance and simulation distance kept apart: the cost sits in what gets simulated. * Client mods pulled out of the mods folder before the first boot. Tech sheet ## NVMe disk by memory step On a large pack it is the disk column that decides the step. 4 GB of RAM 30 GB NVMe R$ 54.00 on the Performance line, with no subdivision. 8 GB of RAM 60 GB NVMe First step with a subdivision, to test an update in parallel. 16 GB of RAM 120 GB NVMe A 900% CPU allocation, for a heavy pack with a full room. Ladder ratio 7.5 GB of NVMe per GB of RAM Holds up to the 64 GB step with 480 GB of disk. Comparison ## What each step costs for the same pack Memory and disk grow together, always at R$ 13.50 per GB of RAM. The processor is the same Ryzen 9 9950X on every step, and that weighs because the main tick is practically a single thread. | RAM step | NVMe disk | Monthly | Annual, per month | | -------- | --------- | --------- | ----------------- | | 8 GB | 60 GB | R$ 108.00 | R$ 97.20 | | 12 GB | 90 GB | R$ 162.00 | R$ 145.80 | | 16 GB | 120 GB | R$ 216.00 | R$ 194.40 | | 24 GB | 180 GB | R$ 324.00 | R$ 291.60 | If you are torn between two steps, let the disk decide: a large pack fills the NVMe before the RAM. Checklist ## Checklist before opening the pack to the community Each item matches a mistake that shows up in support every week. * Download the server pack from the files tab, not the client zip. * Check whether a shader, a minimap or an interface mod was left in the mods folder. * Align the memory in user\_jvm\_args.txt with the step you bought. * Accept the EULA in eula.txt before the first boot. * Set view distance and simulation distance in server.properties. * Measure the memory peak and the directory size after a busy night. * Write down the exact pack and loader version before any update. ## Frequently asked questions 01 How much RAM does my modpack need on the server? The recommendation on the pack page was measured on the client, with one person playing. On the server the rendering cost drops out and the cost of keeping each player chunks and entities comes in. Take that value as the floor and confirm it with the consumption of a busy night. 02 Can I install a Modrinth pack or only a CurseForge one? Both work. On CurseForge you use the server pack from the files tab. On Modrinth you use the .mrpack, resolved by mrpack-install or packwiz at the exact declared version. With no ready server version, remove the client mods by hand. 03 Which step has enough disk for a large pack? Disk follows memory at 7.5 GB of NVMe per GB of RAM: 8 GB comes with 60 GB, 12 GB with 90 GB and 16 GB with 120 GB. Add up mods, the world with all its dimensions, and backups. Three full copies of a 12 GB server already ask for more than 36 GB. 04 Can I update the pack version without losing the world? Sometimes yes, never without a copy. If the new version removes mods, the blocks are left orphaned in the chunks already generated and the loader asks for a confirmation that deletes them. Test it first on a separate instance, which the subdivision included from 8 GB up allows. Keep reading ## Guides that go deeper into each step * [How much RAM a Minecraft modpack needs](https://streethosting.com.br/en/guides/minecraft/how-much-ram-does-a-minecraft-modpack-need) * [How to install a CurseForge modpack on a Minecraft server](https://streethosting.com.br/en/guides/minecraft/install-curseforge-modpack-on-minecraft-server) * [How to pre generate chunks on a Minecraft server with Chunky](https://streethosting.com.br/en/guides/minecraft/pregenerate-chunks-minecraft-chunky) * [How to read the crash report of a Minecraft server](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report) 4.7/5 on Trustpilot Money-back guarantee Activation in 60s Premium support Trusted by 2,500+ customers ## Still unsure about the step? * Send the pack name and version to support and the team points at the step. * Changing step is a plan adjustment, with no server migration and no world regeneration. * Support in Portuguese for boot crashes and conflicts between mods. [See RAM and disk on every step](https://streethosting.com.br/en/minecraft-pro#plans) [Contact support](https://streethosting.com.br/en/contact) Put the pack up and look at the directory size at the end: that number decides the step, not the installer recommendation. ## A strategy for Forge and Fabric without the bottleneck ### Minecraft modpack hosting in Brazil, focused on stability Ryzen 9 plus Gen4 NVMe cuts the delays that show up in large packs. With heap tuning you avoid drops caused by memory spikes and give players a better time during events and exploration. ### Forge servers in Brazil for heavy packs On Forge with many mods, the biggest risk is losing TPS during entity and chunk spikes. Our initial guidance helps you prioritise performance without giving up modpack features. [See our dedicated Forge hosting](https://streethosting.com.br/en/minecraft-forge). ### Fabric servers in Brazil for clean performance Fabric servers usually strike an excellent balance between performance and flexibility. With low latency in São Paulo, gameplay feels more responsive for a Brazilian audience. [See our dedicated Fabric hosting](https://streethosting.com.br/en/minecraft-fabric). [Get Minecraft modpack hosting in Brazil](https://streethosting.com.br/en/minecraft-pro#plans)