Entity Culling — the Async Occlusion Test That Hides What You Can't See
Fabric · Forge · NeoForge · client-side only

Entity Culling: skip the work you'd never see

Minecraft renders entities you cannot actually see — mobs behind walls, chests underground, projectiles outside your field of view. Entity Culling runs an async visibility test for each one and skips rendering the ones that fail. No render-distance cut, no texture change, no visual loss. The only thing that changes is the GPU's workload — and the FPS counter, if the scene is busy enough.

Fabric / Forge / NeoForge Minecraft 1.21.4 Client-side only Performance mod

Quick facts

CategoryPerformance / Rendering
LoadersFabric, Forge, NeoForge
Minecraft1.21.4 and older supported versions
Authortr7zw
SourceCurseForge
Downloads232.2M (CurseForge, Sep 2026)
SideClient-side only

Source status

Verified

The download below is the file listed in our catalogue. Metadata last checked November 2026.

View on CurseForge →

Opens CurseForge in a new tab. CurseForge's terms apply.

Minecraft Mod

Skip the work you'd never see

Entity Culling screenshot showing a crowded mob farm with hidden mobs behind stone blocks, and the FPS counter showing the gain from culled entities
Entity Culling in a crowded mob farm: the mobs behind the stone walls are still simulated server-side, but their rendering is skipped on the client. The FPS counter on the right shows the gain — the mod's only visible effect.
External link

Get Entity Culling

One JAR per loader. Drop into mods for Fabric, Forge, or NeoForge — client-side only, no server install needed.

Visit Entity Culling

File: entity-culling.zip · External — creator's site · No redirects, no ads

What "async path-tracing" actually means here

The name is misleading if you read it literally. Entity Culling does not path-trace light. It runs a visibility check — a ray from your camera to each entity — and asks a simple question: is there a solid block between the camera and this entity? If yes, the entity is occluded, and its render call is skipped. The check runs on a separate thread, so the main render loop never waits for it. That is the "async" part.

The practical consequence is that the mod's cost is paid off the main thread, and its benefit is paid on it. A busy mob farm with 200 entities behind stone generates 200 render calls in vanilla. With Entity Culling, most of those calls are skipped, and the GPU spends its frame budget on the entities you can actually see. The async thread does the bookkeeping; the main thread gets the savings.

That is also why the gain is scene-dependent. A mob farm sees a large improvement because the ratio of hidden to visible entities is high. A quiet plains biome with three cows sees almost nothing, because there is nothing to cull. The mod does not make slow scenes faster — it makes crowded scenes stop paying for entities that are not on screen.

Where the gain actually shows up

Three scenes where Entity Culling tends to pay off, and one where it tends not to:

  • Mob farms. The classic case. Hundreds of entities behind stone, almost none of them visible. The mod culls most of them, and the FPS gain is measurable.
  • Crowded servers. Player-built towns, market districts, and hub worlds with dozens of entities in range. The occlusion test finds more hidden entities than you would expect.
  • Heavy modpacks with block entities. Chests, signs, machines, and Create contraptions all count as block entities. Entity Culling catches block entities too — a detail many rendering optimizers miss.
  • Quiet singleplayer exploration. Not where the mod pays off. Three cows in a field are not a rendering bottleneck, and the culling test will find nothing to skip.

The rule of thumb: if your FPS drops specifically when a lot of entities are nearby — not when the render distance is high, not when a shader is loaded, but when there are mobs in range — Entity Culling is the right tool. If your FPS is low everywhere, the problem is elsewhere.

What it culls

1
EntitiesMobs, items, and projectiles that are occluded by blocks. The core case the mod was built for.
2
Block entitiesChests, signs, and machines that are not visible. Many rendering optimizers miss these — Entity Culling does not.
3
Async visibility testThe occlusion check runs on a separate thread, so it does not steal frames from the main render loop.
4
Whitelist configA config screen for entities you want to always render, even when occluded — useful for modded entities with unusual renderers.

How to install it (client-only, no server step)

Entity Culling is a client-side mod. The server does not need it, and joining a vanilla or modded server will not cause a desync or rejection. The install is the same as any other mod JAR.

  1. Download the JAR matching your loader — Fabric, Forge, or NeoForge. The JARs are not interchangeable.
  2. Download the JAR matching your Minecraft version. Entity Culling ships separate builds per MC version; loading the wrong one will crash on startup.
  3. Drop the JAR into .minecraft/mods (or your launcher's mods folder for the profile you are using).
  4. Launch the game. The mod works silently — no HUD, no button, no visible change. You will only notice it in the FPS counter when a scene has a lot of hidden entities.
Client-side only. The server does not need Entity Culling installed, and installing it will not cause a vanilla server to reject you. It only affects what your client renders — nothing syncs to other players.

Compatibility at a glance

Every value below comes from the creator's official source page. Where the creator doesn't state a field, we mark it "Unknown" rather than guess.

FieldValue
CategoryPerformance / Rendering
LoadersFabric, Forge, NeoForge
Minecraft versions1.21.4 and older supported versions
SideClient-side only
SourceCurseForge (tr7zw)
Downloads232.2M (CurseForge, Sep 2026)
Last verifiedNovember 2026

Frequently asked questions

Does Entity Culling change how the game looks?
No. It only skips rendering work for entities that are already invisible — behind walls, underground, or outside your field of view. Anything you could have seen before, you still see.
Do I need Entity Culling on the server?
No. Entity Culling is client-side. The server does not need it installed, and it won't cause desync or rejection if you join a vanilla or modded server.
How much FPS does Entity Culling add?
The gain depends on the scene. Busy worlds with many entities — mob farms, crowded servers, villages — see the biggest improvement. In a quiet singleplayer world, the difference may be minimal.
Which loaders does Entity Culling support?
Entity Culling supports Fabric, Forge, and NeoForge. Choose the JAR matching your loader and Minecraft version.
Can I whitelist specific entities?
Yes. The mod includes a config screen where you can whitelist entities that should always render, even when occluded.

Why this listing exists

Most resource sites either dump hundreds of unverified links with no context, or hide downloads behind fake countdown timers and redirect chains. This page follows a different approach: it shows the resource's real metadata, links to the creator's original page, and states clearly what we have and have not verified.

If you find a broken link, an incorrect version, or a download that goes somewhere unexpected, report it using the contact form. If you are the creator and want this listing removed or changed, see Copyright / DMCA.

Related mods

Report a problem with this page: contact form. If you are the creator and want this listing changed, see Copyright / DMCA.