Best Minecraft Server Settings for Performance in 2026

Your Minecraft server lagging? FPS dropping? These simple settings will fix most performance issues without installing a single mod or plugin.

Let me show you the exact settings that actually matter for smooth gameplay.

Why Settings Matter More Than You Think

Most people jump straight to "what hosting should I buy?" but ignore settings.

Reality: Good settings on okay hosting > bad settings on expensive hosting.

These tweaks are FREE and take 10 minutes. Do these FIRST before spending money.

Server Performance Settings (server.properties)

Edit your server.properties file. These are the most important settings:

View Distance - THE Most Important Setting

view-distance=10

What it does: How far players can see chunks

Why it matters:

• Default is usually 10-32 (way too high)
• Each increase = exponentially more server load
• Most players don't notice difference between 10 and 16

Best values:

• Vanilla server: 10
• Modded server: 8
• Heavy modpack: 6-8
• Struggling server: 6

Going from 16 to 10 can DOUBLE your TPS. Seriously.

Simulation Distance - New in 1.18+

simulation-distance=8

What it does: How far away chunks still "work" (mobs move, crops grow)

Why it matters:

• Separate from view distance
• You can SEE far but things only work nearby
• Huge performance impact

Best values:

• Normal server: 8
• Busy server: 6
• Struggling server: 4

Players can still see far but server doesn't simulate everything.

Max Tick Time

max-tick-time=60000

What it does: How long before server considers a tick "hung" and crashes

Why change it:

• Default 60000 (60 seconds) is fine
• If server crashes with "Can't keep up" errors, increase to 120000
• Prevents crashes from temporary lag spikes

Network Compression Threshold

network-compression-threshold=256

What it does: When to compress network packets

Best value: 256 (default is good)

• Lower = more compression = less bandwidth, more CPU
• Higher = less compression = more bandwidth, less CPU

Leave at 256 unless you have bandwidth issues.

Entity Broadcast Range

entity-broadcast-range-percentage=100

What it does: How far entities are sent to clients

Performance tweak:

• Lower to 80-90 for big servers
• Players won't see distant entities = less lag
• Most don't notice

World Generation Settings

These affect NEW worlds only (edit before creating world):

Max World Size

max-world-size=10000

What it does: Limits world border

Why limit it:

• Prevents infinite exploration = infinite chunk generation
• Keeps world file manageable
• Good for small servers

Recommended:

• Friend server: 5000-10000
• Community server: 15000-20000
• Public server: 25000+

Spawn Protection

spawn-protection=0

What it does: Radius around spawn where only ops can build

Performance tip: Set to 0 if you don't need it

• Slightly less checking = tiny performance gain

Mob and Entity Settings

Control how many mobs/entities exist:

Spawn Limits (in bukkit.yml or spigot.yml)

spawn-limits:
  monsters: 50
  animals: 10
  water-animals: 5
  water-ambient: 5
  ambient: 5

What it does: Max mobs per player

Performance values:

• Monsters: 50 (default 70)
• Animals: 10 (default 15)
• Water: 5 (default 10)

Fewer mobs = better TPS, players barely notice difference.

Entity Activation Range (Spigot/Paper)

entity-activation-range:
  animals: 16
  monsters: 24
  raiders: 48
  misc: 8

What it does: How close player must be for entity to "work"

Best for performance:

• Animals: 16 (they don't need to move far away)
• Monsters: 24 (still attack when close enough)
• Misc: 8 (item frames, armor stands)

Client-Side FPS Settings

Settings players should change in their game:

Video Settings

Render Distance: Match server view distance

• If server is 10 chunks, set client to 10
• Going higher does nothing but waste FPS

Graphics: Fast (not Fancy)

• Fancy adds unnecessary visual effects
• Fast gives same gameplay, better FPS

Smooth Lighting: Off or Minimum

• Looks slightly worse
• Major FPS boost

Particles: Decreased or Minimal

• Fewer particles = better FPS
• Still see important particles

Entity Shadows: Off

• Looks cool but tanks FPS
• Not worth the cost

Performance Settings

Max Framerate: VSync or 60 FPS

• Don't run unlimited FPS
• Wastes resources, causes stuttering
• 60 FPS is perfectly smooth

Mipmap Levels: 0 or 1

• Higher = blurry distant textures
• Lower = sharper, better FPS

Biome Blend: 5x5 or Off

• Smoother biome transitions but FPS cost
• Most don't notice difference

OptiFine/Sodium Settings

If using performance mods:

With Sodium (better than OptiFine in 2026):

• Enable all performance options
• Disable fancy stuff (clouds, rain, etc)
• Massive FPS boost

With OptiFine:

• Performance > Smooth FPS: ON
• Performance > Smooth World: ON
• Quality settings to Low/Off

Server Software Choice

The server software matters MORE than most settings:

Vanilla (official Minecraft server):

• ❌ No optimizations
• ❌ No plugins
• Only use for pure vanilla testing

Spigot:

• ✅ Basic optimizations
• ✅ Plugin support
• Okay for small servers

Paper (BEST for performance):

• ✅ Heavy optimizations
• ✅ Better than Spigot
• ✅ Same plugins as Spigot
• Use this for most servers

Purpur (best for customization):

• ✅ Paper + more features
• ✅ Extra configuration options
• Great for advanced users

For modded (Forge/Fabric):

• Use Magnesium/Rubidium for Forge
• Use Lithium/Sodium for Fabric
• Optimization mods are essential

Quick Performance Checklist

Do these IN ORDER for maximum impact:

Server Side:

• [ ] Set view-distance to 10 or lower
• [ ] Set simulation-distance to 8 or lower
• [ ] Use Paper instead of Vanilla
• [ ] Lower mob spawn limits
• [ ] Set entity activation ranges
• [ ] Pre-generate world (prevents chunk gen lag)
• [ ] Set world border
• [ ] Regular restarts (clears memory leaks)

Client Side:

• [ ] Match render distance to server
• [ ] Graphics: Fast
• [ ] Particles: Decreased
• [ ] Entity Shadows: Off
• [ ] Max FPS: 60 or VSync
• [ ] Install Sodium (Fabric) or OptiFine
• [ ] Close unnecessary programs
• [ ] Allocate 4-6GB RAM to Minecraft

Pre-Generation - The Secret Weapon

What is it: Generating chunks BEFORE players explore

Why it matters:

• Chunk generation = massive lag
• Pre-gen removes this lag
• One-time cost for permanent benefit

How to do it:

With Chunky plugin:

/chunky world <world-name>
/chunky radius 5000
/chunky start

Let run for 6-12 hours. Your server will thank you.

Performance Monitoring

How to check if settings are working:

TPS (Ticks Per Second)

Command: /tps (with plugin) or check console

What's good:

• 20 TPS = Perfect (target this)
• 19-20 TPS = Excellent
• 18-19 TPS = Good
• 17-18 TPS = Noticeable lag
• Below 17 = Bad, fix issues

Memory Usage

Command: /mem or check hosting panel

What to watch:

• Using 80-90% of RAM = Fine
• Hitting 100% = Need more RAM
• Constant 100% = Crashes incoming

Player Lag

Ask players about:

• Block lag (blocks reappearing)
• Movement lag (rubber-banding)
• FPS drops

Common Performance Myths

Myth: "More RAM = Better Performance"

Truth: RAM only matters if you're running out

• 8GB server using 6GB won't benefit from 16GB
• CPU and settings matter more
• Only add RAM if actually needed

Myth: "Expensive hosting is always better"

Truth: Settings matter more than hardware (to a point)

• Good settings on €5 hosting > Bad settings on €20 hosting
• But there's a minimum hardware threshold

Myth: "Render distance should match view distance"

Truth: Can be different on client vs server

• Server: 10 chunks
• Client: 16 chunks (only uses server's 10)
• Client setting doesn't increase server load

Budget-Friendly Performance

Can't afford expensive hosting? These settings help:

view-distance=6
simulation-distance=4
max-players=10
entity-broadcast-range-percentage=75

Plus:

• Use Paper server
• Pre-generate world
• Limit mob spawns
• Regular restarts

Can make €5/month hosting feel like €15/month hosting.

When Settings Aren't Enough

If you've optimized everything and still lag:

Signs you need better hosting:

• TPS constantly below 18 despite tweaks
• Crashes when chunk generating
• Can't handle your player count
• Modded server with weak CPU

Solutions:

• Upgrade RAM (if using 90%+)
• Get faster CPU (if TPS is low)
• Switch to dedicated resources (if shared)

Check Space-Node's Minecraft hosting for performance-focused hosting from €0.90/month.

Or for heavy modpacks, their VPS plans have Ryzen 9 CPUs perfect for performance.

Settings Template for Different Server Types

Vanilla Survival (10 players)

view-distance=10
simulation-distance=8
max-tick-time=60000
spawn-protection=0
max-world-size=10000

Modded Server (Heavy pack)

view-distance=8
simulation-distance=6
max-tick-time=120000
spawn-protection=0
max-world-size=15000

Large Community Server (30+ players)

view-distance=8
simulation-distance=6
max-tick-time=60000
network-compression-threshold=512
entity-broadcast-range-percentage=85

Final Thoughts

Performance isn't about ONE setting. It's about:

1. Server settings (view distance, simulation distance)
2. Server software (Paper > Spigot > Vanilla)
3. World management (pre-generation, world border)
4. Entity control (spawn limits, activation ranges)
5. Client optimization (Sodium, proper settings)

Do ALL of these and your server will run 2-3x better.

Most lag comes from bad default settings, not bad hardware. Fix the settings first, then consider upgrading hosting if needed.

Your players will notice the difference immediately. Smooth gameplay > slightly prettier graphics every time.