- Top Pick: Hyperkin Admiral Premium BT Controller for N64
- Runner-up: Samsung T7 Portable SSD 1TB
- Also consider: SanDisk 128GB Ultra microSDXC UHS-I Card
Nintendo 64 games were built for CRT televisions, and their textures show it: many are tiny 32 by 32 or 64 by 64 pixel images that turn to soup on a modern monitor. HD texture packs fix that by swapping in fan-redrawn artwork at several times the original resolution, making a familiar game look startlingly clean. The catch: installation is fussier than dropping a file into a folder, because the two main routes, Project64 and RetroArch, handle packs differently.
As an Amazon Associate, we earn from qualifying purchases.
This guide walks through both routes step by step, explains why packs silently refuse to load when the version or folder name is wrong, and covers the memory and loading costs. Everything here assumes you are playing dumps of cartridges you own; a texture pack contains artwork only and is useless without your own copy of the game.
This article contains affiliate links, and we may earn a commission if you buy through them at no extra cost to you.
Quick Answer
N64 HD texture packs replace a game’s original low-resolution textures with fan-made high-resolution artwork. In Project64, select GLideN64, enable Use Texture Pack, and place the pack in the plugin’s hires_texture or cache folder. In RetroArch, load the game with the Mupen64Plus-Next core, turn on Use High-Res Textures in core options, and put the pack’s cache file in the Mupen64Plus cache folder.
How Texture Replacement Actually Works
The N64 stores its textures inside the game data, and every time the console draws a scene it uploads those small images to the graphics chip. GLideN64, the graphics plugin behind both routes in this guide, sits in the middle. As each texture passes through, the plugin calculates a checksum for it and checks for a replacement with the same checksum in the pack. If one does, the high-resolution version is drawn instead of the original.
That checksum matching explains the two rules that govern every pack. First, a pack only works with the exact game version it was made for, because a different region or revision changes the textures and their checksums. Second, packs ship in two formats. Loose packs are folders of PNG files in the layout pioneered by the old Rice plugin, hence Rice format. Compiled packs are single cache files, ending in .htc or, in newer GLideN64 builds, .hts, which bundle a whole pack for faster loading.
Route One: Project64 with GLideN64
Project64 is the more forgiving route, and the one most pack authors document, because GLideN64 there both loads packs and compiles loose folders into cache files.
- Open Options, then Settings, then Plugins, and set the video plugin to GLideN64.
- Open Options, then Configure Graphics Plugin, and find the Texture enhancement tab. Turn on Use Texture Pack and Use full transparencies. For a reusable cache file, also turn on Compress texture cache and Save enhanced texture cache to hard disk.
- For a loose Rice-format pack, extract it so the folder named with the game’s internal name, for example THE LEGEND OF ZELDA, sits inside Plugin, GFX, GLideN64, hires_texture. For a precompiled pack, place the cache file, named like THE LEGEND OF ZELDA_HIRESTEXTURES.htc, in the GLideN64 cache folder instead.
- Start the game and wait. On the first launch GLideN64 compiles the loose textures into a cache, which can take several minutes on a large pack and may look like a hang. Later launches load the cache and start quickly.
- If the game looks unchanged, check the folder name first: it must match the game’s internal name exactly, which is not always your dump’s file name, and the pack must match your version and region.
Route Two: RetroArch with Mupen64Plus-Next
In RetroArch the work is done by the Mupen64Plus-Next core, which uses GLideN64 internally. Load your game with that core, open the Quick Menu, and enter Options. Turn on Use High-Res Textures, and set Use High-Res Full Alpha Channel as the pack’s documentation specifies, since packs differ on it.
Precompiled cache files go in the cache folder inside the Mupen64Plus folder in RetroArch’s system directory, with a file name matching the game’s internal name. The core can also read a loose Rice-format folder placed in the Mupen64Plus hires_texture folder and build its own cache. One warning: a precompiled cache only loads when the texture settings, such as cache compression and the alpha channel option, match the settings used when the cache was created. If a known-good pack is ignored, the most reliable fix is to compile it yourself in Project64 with compression on, then copy the resulting .htc file across. Save a game override once a pack works so the settings stay attached to that title.
Dumping Your Own Textures
If you want to redraw textures yourself, GLideN64 can supply the raw material. Its texture enhancement settings include a dumping option: while enabled, the plugin writes the game’s original textures out as PNG files as they appear during play. Artists repaint those files at a higher resolution, keeping the original file names so the checksums still match, then share the folder as a Rice pack or compile it into a cache. Play through varied areas before switching it off, because textures only appear once the game shows them.
The Costs: Memory, Loading and Clashes
Texture packs are not free. A large pack’s cache file can run to hundreds of megabytes on disk, and the decompressed textures live in system memory and graphics memory while you play, so the largest packs are a poor match for low-memory machines. The first-load compile is a one-off cost, but loose packs re-check their files at every startup.
There are visual costs too. Packs redraw the interface as well as the world, and a redrawn HUD or font can sit awkwardly with a widescreen hack or a stretched aspect ratio, because the author usually designed it for the original 4:3 frame. Some packs also only cover part of a game, so original and redrawn textures can appear side by side in later areas. None of this breaks a game, but expect a sometimes patchy remaster rather than a uniform one.
Where Packs Come From
Packs are distributed by their authors through community forum boards dedicated to completed texture projects and through release pages on code-hosting sites. A legitimate pack contains only artwork: PNG images, or a cache file built from them. It never contains the game itself, and you still need a dump of your own cartridge for the pack to attach to. Treat any download that bundles game data as one to walk away from.
Gear That Supports Texture Pack Play
Hyperkin Admiral Premium BT Controller for N64
The Admiral keeps the single central stick and six-button face of the original pad in a modern two-handed shell, which matters when a pack tempts you into replaying a whole game. It connects by Bluetooth through its included dongle, which also accepts a memory card and backs up its saves to a microSD card.
Specs:
- Model: M07389-BK
- Connection: Bluetooth via included dongle
- Battery life: approximately 6 hours
- Compatibility: N64, PC, Mac, Android
- Weight: 12.8 ounces
8BitDo Pro 2 Bluetooth Controller
If you prefer a modern pad, the Pro 2 maps well to N64 games because its right stick can stand in for the four C buttons, which suits games that use them for camera control. Hall Effect sticks resist drift, and its mapping software supports per-game profiles.
Specs:
- Connection: Bluetooth and USB-C wired
- Sticks: Hall Effect analog sticks
- Compatibility: Windows, Switch, macOS, Android
- Battery: rechargeable, maker-rated up to 20 hours
- Extras: 8BitDo Ultimate Software for remapping
Samsung T7 Portable SSD 1TB
Cache files grow quickly, and a fast portable SSD keeps packs, dumps of your own cartridges and emulator folders in one place that moves between machines. The T7 reads at up to 1,050 MB/s over USB 3.2 Gen 2, so copying a multi-game collection takes minutes.
Specs:
- Capacity: 1 TB
- Model: MU-PC1T0T/AM
- Interface: USB 3.2 Gen 2
- Read speed: up to 1,050 MB/s
- Encryption: AES 256-bit hardware encryption
SanDisk 128GB Ultra microSDXC UHS-I Card
RetroArch setups on handhelds and single-board computers keep their system folder, including the Mupen64Plus cache folder, on microSD. This 128 GB card is Class 10 and A1 rated, and doubles as the save backup card for the Admiral dongle above.
Specs:
- Capacity: 128 GB
- Model: SDSQUAB-128G-GN6MA
- Read speed: up to 140 MB/s
- Speed class: Class 10, U1, A1
- Includes: full-size SD adapter
One by Wacom CTL-672 Pen Tablet
For readers who want to redraw textures rather than only install them, a pen tablet is the tool most pack artists work with. The CTL-672 offers an 8.5 by 5.3 inch active area, room for detailed strokes without taking over a desk, and a pen that needs no battery or charging.
Specs:
- Model: CTL-672
- Active area: 8.5 x 5.3 inches
- Size: 10.9 x 7.4 x 0.3 inches
- Weight: 420 g
- Pen pressure levels: not stated
How to Choose
Start with the route, not the pack. If you already live in RetroArch, stay there and favour precompiled cache files, or be ready to compile loose packs in Project64 once. If you are setting up fresh, Project64 with GLideN64 is the documented path most authors test against.
Then match three things before downloading: the game’s exact version and region, the format the pack ships in, and the settings its author used, especially cache compression and the full alpha channel option. Finally, weigh pack size against your hardware. A modest pack at twice or four times the original texture size transforms a game on almost any PC, while the largest packs punish machines without memory to spare.
Who Should Skip
Skip texture packs if your games run on a low-memory handheld that already struggles with the Mupen64Plus-Next core, because the added memory load lands on the same hardware. Skip them if you play with widescreen hacks and patches as your priority, since redrawn interfaces often assume the original frame. And skip them if matching versions, folder names and cache settings sounds like a chore, because the original textures remain perfectly playable.
FAQ
Why does my texture pack not load at all?
The usual causes are a folder or file name that does not match the game’s internal name, a pack built for a different version or region, or cache settings that differ from those used to compile the pack. Check the name first, then the version, then recompile the pack yourself with compression enabled.
Do texture packs slow games down?
They can on modest hardware. The first launch of a loose pack is slow while the cache compiles, and large packs use more memory during play. Once a cache exists and your machine has headroom, frame rates are usually close to stock.
Are texture packs legal to download and use?
A pack contains fan-made artwork only, and downloading artwork is not the problem area. The legal line is the game itself: packs assume you supply a dump of a cartridge you own. Avoid any source that bundles game data.
Can I use the same pack in Project64 and RetroArch?
Often, yes. A cache file compiled by GLideN64 in Project64 can be copied into the Mupen64Plus cache folder for RetroArch, provided the name matches the game’s internal name and your core options match the compile settings, including cache compression.
Final Verdict
N64 HD texture packs are the single biggest visual upgrade available to N64 emulation, and they cost nothing but setup care. Project64 with GLideN64 is the easiest place to install and compile packs, while RetroArch with Mupen64Plus-Next runs the same cache files once its core options are set. Match the pack to your exact game version, respect the first-load compile time, and your own cartridge library gains a second life at modern resolutions.










