Most bots need far less than people buy. Memory use is driven by how much of Discord your bot keeps in memory and what it does besides talking to Discord — not by how many commands it has.
Realistic starting points
| Bot | Memory |
|---|---|
| Commands, moderation, a few servers | 512 MB is comfortable |
| Music playback | 1–2 GB — audio buffers and encoding are the cost |
| Member caching across many servers | 1–2 GB, rising with member count |
| Image or video generation | 2 GB+, depending entirely on the library |
| A bot in hundreds of servers | 2–4 GB, mostly cache |
What actually consumes it
Caching is the big one. A client that holds every member of every guild grows with your reach, and most bots never read most of that. Turning off the caches you do not use is usually a bigger win than adding memory.
The other is anything that processes media. Audio and images are handled in buffers that dwarf everything else your bot does.
The panel shows live memory use. Run the bot for a week and look at the peak, not the average — the peak is what has to fit. Buying on a guess is how people end up paying for four times what they use.
If usage climbs steadily and never falls, more memory buys you a longer wait before the same crash. Steadily-rising memory in an idle bot is a bug — usually an array or a Map that gets appended to and never cleared.