Can I Run Minecraft (Java) on My PC / Laptop?

Almost certainly, yes. Minecraft's official minimum, an Intel HD 4000 or Radeon R5, a Core i3-3210 or A8-7600, and 4 GB of RAM, is a bar most PCs from the last decade clear without trying. Run your own CPU and graphics card through the checker above to see exactly where you land.

A Core i3-3210 or AMD A8-7600 processor, an Intel HD 4000 or Radeon R5 graphics card, and 4 GB of RAM. That's enough for vanilla survival at default render distance, not for shaders or heavy modpacks.

Mojang lists a Core i5-4690 or AMD A10-7800 processor, a GeForce 700 series or Radeon Rx 200 series graphics card, and 8 GB of RAM. That covers vanilla comfortably; add shaders and you'll want more RAM and a newer GPU than either of those.

8 GB of system RAM covers vanilla comfortably, with 4 GB allocated to Java. Add a modpack or shaders and 16 GB total is the more realistic target, since you need headroom for your OS on top of whatever you give Minecraft.

For vanilla, yes. You'd typically allocate 3 to 4 GB to Java and leave the rest for Windows or macOS. Once you add a modpack with dozens of mods, 8 GB total starts to feel tight and you'll notice more stutter.

Yes, for most setups. 16 GB lets you allocate 6 to 8 GB to Java for a shader pack or a moderate modpack while keeping enough free for the OS. Very large modpacks with 200-plus mods can push past that, but 16 GB covers the vast majority of players.

4 GB for vanilla, 6 to 8 GB for a handful of mods or a light Fabric setup, and 8 to 12 GB for a heavy modpack. You set it in the Installations tab of the official launcher. Giving Java far more than it needs can cause its own stutter from garbage collection, so more isn't automatically better.

You can skip it. A hard drive handles the base game fine, and an SSD's real benefit is snappier world loading and chunk generation, something that matters more once you're running large modpacks or big multiplayer worlds with heaps of saved chunks.

About 1 GB for the base install. Once you add worlds, resource packs, and a mod loader like Fabric or Forge, figure closer to 5 to 10 GB, and large modpacks with high-resolution texture packs can go well beyond that.

No. The official Minecraft Launcher bundles its own Java runtime and manages the version automatically. You only need to install or select Java yourself if you use a third-party launcher like Prism Launcher or MultiMC, or if you're running a dedicated server jar directly.

It depends on the game version, and Mojang has raised it over time: Minecraft 1.21 and newer require Java 21, versions from 1.18 through 1.20.4 needed Java 17, and anything before 1.17 ran on Java 8. The official launcher handles this for you, so it only matters if you manage Java manually.

Because its renderer was built around a single CPU thread doing most of the world generation, lighting, and chunk building, with the GPU mostly just drawing what the CPU hands it. That's why an old CPU paired with a new GPU still runs badly, and why performance mods like Sodium target CPU-side rendering code rather than graphics settings.

It's Mojang's combined purchase that gives you both the Java Edition and the Bedrock Edition through one Microsoft account and one launcher, so you can play whichever suits a given world or server without buying twice. This page focuses on Java, since that's the version with mod and shader support.

Check your CPU and RAM allocation before you blame the graphics card. If you're on an old dual-core CPU, that's your ceiling for vanilla and shaders alike. If your CPU is decent but fps still tanks with shaders on, that's when a GPU upgrade actually helps.

Yes. On the RTX 3050, Minecraft (Java) runs at high settings in 1080p and scales up to 1440p without much fuss.

It will run. The GTX 1650 meets Minecraft (Java)'s minimum, which means 1080p on low to medium and a smoother result once you lower a couple of options. Vanilla runs well past 150 fps. Mid-weight shaders land around 45 to 55.

No trouble at all. The GTX 1060 6GB meets or beats what Minecraft (Java) recommends, so 1080p high runs well and 1440p is realistic. Vanilla is a non-issue at 200-plus fps. Mid shader packs run 55 to 70, and heavier packs drop into the 30s.

Fine for a lighter setup. The RX 580 clears Minecraft (Java)'s minimum, so target 1080p low to medium and adjust down for a steady rate. Vanilla is easy. Mid shader packs run around 40 to 50 fps.

Yes, with room to spare. Minecraft (Java) recommends less than the RTX 4060 offers, so expect smooth 1080p high and a playable 1440p. Vanilla and most shaders are trivial. Path-traced packs stay around 60 to 70.

The RTX 3060 is a strong fit for Minecraft (Java). It lands at or above the recommended spec, so high 1080p is comfortable and 1440p works. Heavy shaders run 70 to 90 fps, and path-traced packs land around 50 to 60.

You are well set. The RTX 2060 exceeds Minecraft (Java)'s recommended card, so 1080p high is easy and 1440p is realistic. Handles most shader packs above 60 fps. Path-traced packs are rougher, closer to 35 to 45.

That is more than enough. The GTX 1660 clears Minecraft (Java)'s recommended requirement, so aim for high at 1080p or step up to 1440p. Comfortable with mid to heavy shader packs, typically 60 to 80 fps at 1080p.

Plenty of power here. The GTX 1660 Super is above Minecraft (Java)'s recommended tier, so high 1080p is smooth and 1440p is a fair target.

The RX 6600 is a strong fit for Minecraft (Java). It lands at or above the recommended spec, so high 1080p is comfortable and 1440p works. Handles mid to heavy shader packs around 60 to 75 fps, though some Nvidia-only path-traced packs won't run on it at all.

Yes. On the GTX 1660 Ti, Minecraft (Java) runs at high settings in 1080p and scales up to 1440p without much fuss.

That is more than enough. The RTX 3060 Ti clears Minecraft (Java)'s recommended requirement, so aim for high at 1080p or step up to 1440p. Similar to the RTX 3060 with more headroom. Heavy shaders comfortably clear 90 fps.

Yes, with room to spare. Minecraft (Java) recommends less than the RTX 4050 offers, so expect smooth 1080p high and a playable 1440p.

It will run. The GTX 1050 Ti meets Minecraft (Java)'s minimum, which means 1080p on low to medium and a smoother result once you lower a couple of options. Vanilla doesn't come close to challenging it, usually 140 or more fps. A light shader pack runs around 40 to 50.

No trouble at all. The RTX 4070 meets or beats what Minecraft (Java) recommends, so 1080p high runs well and 1440p is realistic. Even path-traced shader packs stay above 70 fps at 1080p.

Yes. Minecraft Java Edition has a native Mac version and runs well on Apple Silicon MacBooks, including the base Air. Vanilla survival is smooth on any M-series chip, and even mid-range shader packs are playable on an M2 or newer thanks to the integrated GPU's memory bandwidth. Heavy path-traced shader packs are still a stretch.

For vanilla play, yes. Intel HD 4000 or newer, or any Radeon integrated chip from the last decade, clears the minimum at default settings and a normal render distance without trouble. Shaders are where it falls apart: light packs are borderline at best, and mid to heavy packs drag fps into single digits on most integrated GPUs.

Only through workarounds. There's no native ChromeOS version, so you either stream it through cloud gaming or enable Crostini (ChromeOS's Linux environment) and install the Minecraft Launcher there, which works but needs the Linux container's GPU acceleration turned on to avoid single-digit fps. It runs decently on Chromebooks with an Intel or AMD chip; Celeron-based Chromebooks struggle even in Linux.

Yes, and it's a first-class platform for it. Java runs the same way on Linux as on Windows or Mac, so vanilla performance is generally on par with Windows once your CPU and RAM meet the requirements. The main friction is getting the right GPU drivers and Java version installed, which most distributions make straightforward through their package manager.

Yes, though not through Steam directly since Java Edition isn't sold there. You switch to desktop mode, install Prism Launcher, and sign in with your Microsoft account. All three handhelds run vanilla comfortably at native resolution; dropping render distance to 8-10 chunks and adding Sodium helps battery life and keeps things stable. Shaders work but shorten battery life fast.

Inconsistently. Nvidia has added and removed Java Edition from GeForce Now's library at different points, and plenty of users report it missing even when Bedrock streams fine. Don't count on cloud streaming as your primary way to play Java Edition; treat it as a backup at best.

Yes, and resolution matters less here than in most games. Since Minecraft is CPU-bound for vanilla play, a GPU that handles 1080p vanilla comfortably will handle 4K vanilla almost as well. With shaders on, 4K does start costing real fps, and you'll want an RTX 3070 or better to stay smooth.

Yes, for essentially the same reason as 4K: vanilla Minecraft's CPU bottleneck means resolution changes have a smaller effect than in GPU-bound games. Any card that clears the recommended spec handles 1440p vanilla without trouble. Shader packs are where 1440p starts to cost meaningful frame rate.

For vanilla, almost any CPU from the last eight years paired with 8 GB of RAM gets you well past 60 fps. For 60 fps with a mid-weight shader pack, aim for a GTX 1060 6GB or better and a Core i5 or Ryzen 5 class CPU. Heavy path-traced shaders at 60 fps want an RTX 3060 or better.

It depends on the pack. Light stylized shader packs run fine on a GTX 1650 or similar. Mid-weight packs want a GTX 1060 6GB or better. Full path-traced packs like SEUS PTGI want an RTX 3060 or better, and several of those packs are Nvidia-only and won't run on AMD or Intel graphics cards at all.

Yes, for vanilla. As long as you're above the Core i3-3210 and Intel HD 4000 minimum with 4 GB of RAM, vanilla survival at a modest render distance is playable. Lower your render distance to 8-10 chunks and skip shaders entirely, since that's where old hardware falls over.

No. Java Edition is PC, Mac, and Linux only. Xbox runs Minecraft Bedrock Edition, which is a different build with cross-play against other consoles, mobile, and Windows, but no support for Java mods or shaders.

No. PlayStation only has Minecraft Bedrock Edition. If you want the Java-specific mods and shader packs covered on this page, you need a PC, Mac, or Linux machine.

No, Switch only has Bedrock Edition. Java Edition has never released on any Nintendo console, and there's no indication that's changing.

Yes, comfortably for vanilla. Intel Iris Xe (found in many recent thin laptops) handles vanilla Minecraft at well over 60 fps at default render distance. Light shader packs are playable around 25-30 fps; anything heavier isn't realistic on it.

Radeon 780M, found in recent Ryzen laptop chips, handles vanilla easily above 100 fps and manages light-to-mid shader packs around 30-40 fps. The older Vega 8 graphics on earlier Ryzen APUs is weaker: vanilla is still fine, but shaders drop into the teens and twenties.

Yes, well above recommended. Vanilla is trivial, mid to heavy shader packs run 70-90 fps, and path-traced packs are playable around 30-40 fps if the pack supports Nvidia's older architecture.

Yes, comfortably. It handles heavy shader packs around 55-65 fps, a step up from the 1070, though it still shows its age against modern path-traced packs.

Yes, well above recommended. Heavy shader packs run 70-80 fps, and lighter path-traced packs are playable around 40-50 fps.

Yes, easily. Heavy shaders run 90-110 fps, and path-traced packs land around 55-70, which is genuinely comfortable territory.

Yes, with plenty of headroom. Heavy shaders clear 110 fps, and path-traced packs run 65-80, well past what most players need.

Yes, and it's overkill for anything short of the heaviest path-traced packs, which still stay comfortably above 90 fps at 1080p. At this point your CPU is doing more to limit fps than the card.

Yes, and the GPU stops being a factor at all. Vanilla, mid shaders, and even path-traced packs run well past 100 fps, so a faster CPU and more RAM allocated to Java are what push numbers higher from here, not a better graphics card.

Yes, for vanilla and most shader packs, running heavy packs around 80-95 fps. A number of Nvidia-only path-traced packs, including SEUS PTGI and Continuum RT, won't run on it at all regardless of how strong the card is.

Yes, for vanilla, since these clear or exceed the official minimum easily. Where it struggles is high render distances and shaders, both of which lean on the CPU more than most games. A modern i3 handles vanilla fine but caps out fast once you push render distance past 16-20 chunks.

Stutter is almost always chunk loading or Java's garbage collector pausing to clean up memory, not a lack of raw power. Check that Java's memory allocation isn't set too low or absurdly high, lower render distance a few chunks, and make sure you're on a recent graphics driver. If the game won't launch at all, it's usually a corrupted install, an outdated Java runtime in a third-party launcher, or a broken mod in your mods folder.

Not reliably. Mojang's official requirements now list Windows 10 or 11, and current versions of the launcher and newer Java releases aren't tested against Windows 7. Older Minecraft versions with an older Java runtime installed manually may still work, but you're on your own if something breaks, and upgrading the OS is the safer path.

You need a one-time purchase and a Microsoft account to log in, since Mojang moved Java Edition accounts over to Microsoft accounts years ago. There's no subscription required to play; Realms (Mojang's hosted multiplayer service) is a separate optional subscription.

No. Java Edition has no mobile version. Android and iOS run Minecraft Bedrock Edition instead, which is a separate build without Java mod or shader support.

Check Video Settings: 'Max Framerate' defaults to a set value on many installs, and Vsync can also lock you to your monitor's refresh rate. Set Max Framerate to Unlimited and turn Vsync off if your monitor supports a higher refresh rate and you want to see uncapped numbers.

Press F3 to open the debug overlay, which shows fps in the top-left corner along with your coordinates, chunk data, and memory usage. There's no need for a separate overlay app unless you want one for recording.

Install Sodium (Fabric) or use OptiFine, both of which rework how the game renders chunks and typically double or triple fps for free. After that, lower render distance, turn off smooth lighting and fancy graphics if you're still struggling, and make sure Java's memory allocation is in the 4-8 GB range rather than left at a tiny default.

60 fps is a comfortable baseline for smooth building and exploring. Competitive PvP players often chase much higher numbers, sometimes into the hundreds or more with Sodium and a strong CPU, since higher fps lowers input latency, but 60 is plenty for normal survival or creative play.

Yes, and the same CPU-and-RAM logic applies, just doubled up since you're now running the client and server at once if you play on the same machine. A dedicated server for a handful of friends runs fine on 2-4 GB allocated to the server jar; hosting for a larger group or with plugins needs more RAM and a CPU that isn't also busy running your game client.