How to Set Up Project64 — Complete N64 Emulator Guide 2026

Why Project64? N64 emulation on PC has been mature for over two decades. Project64 runs the vast majority of the ~400-game N64 library with high compatibility, supports modern enhancements like HD texture packs and widescreen, and works on virtually any PC built in the last decade. Top titles: Super Mario 64, Zelda Ocarina of Time/Majora's Mask, GoldenEye 007, Mario Kart 64, Banjo-Kazooie, Donkey Kong 64.

Step 1 — Download Project64:

Official source: project64.com. Download the installer for Windows (Project64-x.x.x-Setup.exe) and run it. As of 2026, the current stable build is Project64 3.x.

⚠ Avoid unofficial mirrors — searching "Project64 download" surfaces many third-party sites that bundle older builds with adware or modified installers. Stick to project64.com or the official GitHub releases page.

Project64 is Windows-only. Linux/macOS users should use Mupen64Plus or RetroArch with the Mupen64Plus-Next core.

No BIOS required: Unlike DuckStation (PS1), PCSX2 (PS2), or RPCS3 (PS3) — which all require real firmware dumps — Project64 uses HLE (high-level emulation) to boot the N64 internally. You do not need any BIOS or firmware file. Just ROMs.

Step 2 — Set up your ROM folder:

On first launch, Project64 opens a ROM browser. Click File → Choose ROM Directory and point it to your N64 ROM folder. Project64 scans and displays your library with title and region labels.

Supported ROM formats:

• .z64 — big-endian, native N64 byte order. Recommended — no byte-swap needed. Most modern dumps are .z64.
• .n64 — little-endian. Also works.
• .v64 — byteswapped. Works; Project64 handles the byte-swap internally.
• .zip / .7z — compressed archives. Project64 extracts on load.

N64 games are legally archivable from cartridges you own using a dedicated dumping device. EmuDesk does not link to ROM download sites.

Step 3 — Verify DirectX and first launch:

N64 emulation is very light — any GPU from the last 10 years handles it at full speed. Double-click any game in the ROM browser to launch. On first run, GLideN64 compiles shaders; expect a brief pause. Subsequent launches are instant.

Project64 3.x ships with GLideN64 as the default graphics plugin — the right choice for all modern setups. It supports Vulkan and OpenGL, handles the N64's Reality Display Processor accurately, and enables visual enhancements not possible on original hardware.

Open graphics settings: Options → Settings → Plugins → Video → Configure (or the Configure button next to the video plugin dropdown).

Internal resolution:

• 2× (640×480): recommended starting point — visible improvement over native 320×240, low GPU overhead. Most N64 games look great at 2×.
• 4× (1280×960): sharpest for close-up textures. Higher than 4× rarely improves the look further due to the low-poly geometry, and may cause graphical glitches in some titles.

Set full-screen resolution to match your monitor's native resolution.

Framebuffer emulation — keep ENABLED: required for games that render UI elements (health bars, maps, mini-maps) into the framebuffer. Disabling it breaks these visual elements in Zelda, Mario Party, and others. Only disable as a last resort for performance on very old hardware.

Texture filtering:

• X2 or Smooth: slightly cleaner look, minimal performance impact.
• None/Nearest: pixel-accurate output — preserves the original look if you prefer it.
• Anisotropic filtering helps on oblique camera angles for floors and terrain.

Aspect ratio: original games are 4:3. Set "Aspect ratio" to 4:3 to preserve the original look. Some GLideN64 builds support "Force 16:9" widescreen — this can clip geometry in games not designed for it; use with caution.

Jabo's DirectX plugin (legacy alternative): ships as a fallback. It is fast but lacks Vulkan, has worse framebuffer accuracy, and receives no updates. There is no reason to use it on a modern PC.

Controller setup:

Project64 uses DirectInput by default. XInput controllers (Xbox 360, Xbox One, Xbox Series) are detected automatically on modern Windows.

For DualSense / DualShock 4: install DS4Windows first to map the PlayStation controller to XInput — without it, Project64 may not detect PlayStation controllers correctly.

Manual mapping: Options → Configure Controller Plugin → select controller slot 1 → click each N64 button label and press the corresponding physical button.

Recommended Xbox controller mapping for N64:

• N64 A → Xbox A
• N64 B → Xbox X
• Z trigger → LT
• L → LB, R → RB
• Start → Start/Menu
• C-Up/Down/Left/Right → Right stick directions
• D-pad → D-pad
• Analogue stick → Left stick

N64 analogue range fix: the original N64 stick has a notoriously narrow range. If games feel too sensitive or sluggish, open the controller config and adjust the "Range" slider for the analogue stick. Values between 70–85 often match original hardware feel. See also: Project64 controller not detected fix

Memory Pak vs Rumble Pak (per-game):

Right-click any game → Edit Game Settings → Controller Plugin → Pak 1: choose Mempak or Rumble Pak.

• Memory Pak required for: Mario Kart 64, Mario Party series, GoldenEye 007 (multiplayer settings), Perfect Dark, Banjo-Kazooie. Without Mempak these games can't save.
• Rumble Pak: vibration feedback. Works if your controller has rumble.

Expansion Pak (8 MB RAM — required by some titles):

Project64 auto-detects the Expansion Pak requirement from the ROM header. If a game reports "Expansion Pak not detected": right-click ROM → Edit Game Settings → RAM Size → 8 MB.

Required by: Zelda Majora's Mask, Donkey Kong 64, Perfect Dark (story mode), Banjo-Tooie, Kirby 64.

Per-game settings (right-click ROM → Edit Game Settings):

• Counter Factor: affects game timing. Default is 2; some older titles need 1 (fixes intro movies playing too fast).
• Self-modifying code: if a specific title hangs on startup with the default "Cache" setting, try "Protected" or "Check Memory."
• Core Style: "Recompiler" (default, fast) vs "Interpreter" (accurate, slow). Interpreter is rarely needed but solves timing bugs in a handful of titles.

Cheats (GameShark): right-click ROM → Edit Cheats → Add Cheat → enter GameShark code in format XXXXXXXX YYYY. Check the box to enable at launch. Cheat databases are at gamehacking.org.

Performance tips:

N64 emulation is very light — slowdowns on modern hardware are rare. If you see them:

• Update GPU drivers. GLideN64 uses GPU-accelerated rendering; outdated drivers cause frame drops even on integrated graphics. See: GPU driver clean-install guide
• Lower internal resolution from 4× to 2× or native. N64 games have frame-rate-dependent physics in some titles — you are still emulating the same 30/60 fps at any resolution.
• Switch Vulkan ↔ OpenGL in GLideN64 — on some integrated GPUs one backend runs significantly faster.
• Counter Factor 1 can marginally speed up games that run slow but introduces timing inaccuracies.
• General slowdown diagnosis: Emulator slow despite strong PC

Mupen64Plus — the accuracy alternative: Mupen64Plus is an alternative N64 emulator aimed at higher accuracy over compatibility breadth. Use it when: you want frame-perfect accuracy for competitive runs; a game doesn't work correctly in Project64; or you are on Linux/macOS (Project64 is Windows-only). RetroArch ships the Mupen64Plus-Next core — a good option if you already use RetroArch for other platforms. For most players running the N64 library casually, Project64 is simpler and works just as well.

Save states and in-game saves: System → Save State (F5) / Load State (F7). For long games (Zelda, Banjo-Kazooie, DK64), always save in-game at save points in addition to save states — if a state file becomes corrupt you lose everything. In-game saves are stored in Project64's Save\ folder.

Common issues:

• Controller not detected — DirectInput vs XInput mismatch. Xbox controllers need no driver. For PlayStation controllers, install DS4Windows. See: Project64 controller fix
• Game hangs on startup / black screen — try right-click ROM → Edit Game Settings → Counter Factor 1, SMC "Protected" mode, or Core Style "Interpreter."
• "Expansion Pak not found" in-game — Edit Game Settings → RAM Size → 8 MB.
• Intro movie plays too fast — Edit Game Settings → Counter Factor → 1.
• Texture glitches / missing surfaces — enable framebuffer emulation in GLideN64 settings.
• Audio crackling or desync — increase audio buffer to 5000ms in the audio plugin config, or switch to AziAudio.
• Controls feel wrong / oversensitive — controller config → Range slider → try 70–80 for analogue stick.
• In-game save not working — Edit Game Settings → Controller → Pak 1 → Mempak.
• "GLideN64 failed to initialize" / GPU driver crash — update GPU drivers. See: GPU driver guide
• Emulator crashes on specific game — check project64.com compatibility DB; try Mupen64Plus or RetroArch Mupen64Plus-Next core.

Quick-start summary:

1. Download from project64.com (Windows installer)
2. File → Choose ROM Directory → point to your N64 ROM folder
3. No BIOS needed — N64 boots via HLE
4. Options → Settings → Plugins → Video → Configure → set internal resolution to 2×
5. Options → Configure Controller Plugin → map buttons; adjust analogue Range to 70–80
6. For Majora's Mask / DK64 / Perfect Dark: right-click → Edit Game Settings → RAM Size 8 MB if needed