Getting Custom Hairstyles Into Your Pokemon Ultra Moon Save
The Pokemon Ultra Moon customization scene revolves around ROM hacking tools and texture mods that replace the default character sprite colors and hair palettes. Most people approach this thinking they just need to drop a couple of files into a folder and launch the game. It doesn't work that way, and the frustration is real if you go in blind. What you're really dealing with is a combination of a patched ROM, a hex editor or ARM7 disassembly knowledge, and a set of palette swap tables that control which hair colors and styles apply to your save file. The base game uses 16-color palettes per sprite tile, and the hairstyle data is embedded in the character creation section of the ROM's data banks. When someone releases a "hairstyle mod," they're usually redistributing a pre-patched ROM or providing a delta patch that modifies those exact bytes.
Pokemon Ultra Moon Hairstyles A Fusion Of Fashion And Fantasy
This is a community ROM hack that bundles together a collection of alternate hairstyles, clothing options, and color palettes for both the male and female protagonists. It pulls from the original sun/moon sprite work and extends it using the same engine structures. The files are scattered across multiple ROM hacking forums, usually hosted onsites like PokeCommunity or Smogon's ROM hacking boards. You'll typically find a .ips or .bps patch file, a README with instructions that assume you already know what you're doing, and sometimes a standalone patched ROM if the author is being generous. Here's the part nobody mentions upfront: the patch only works cleanly if your base ROM is the exact version it was built against. Ultra Moon has regional variants (NTSC-U, PAL, JAP), and the memory addresses shift between them. I learned this the hard way when I tried applying the patch to a PAL ROM I'd picked up for the region-exclusive content. The game booted fine, but every character had the wrong hair, the menu text was scrambled, and half the NPCs had tiling errors that looked like static. It took me about forty minutes to realize the patch was written for the US dump, which I confirmed by checking the ROM header checksum against the patch documentation. The workaround was straightforward once I figured it out. I grabbed a clean NTSC-U ROM, verified the MD5 hash matched what the patch author listed, applied the patch with an xdelta or BPSTool depending on the file format, and then ran a quick test in the character creation screen before committing any play time. That second check alone has saved me from several botched installs over the years.
One thing that catches people off guard is that these hairstyle mods don't just change appearance. They can affect sprite overlap in battles, and in some cases they interfere with the move animation frames if the hair sprite extends into the attack hitbox area. I noticed this with one particular mod where the long flowing hair sprites for the female protagonist would clip through the Thunderbolt animation in certain frame positions, making it look like the electricity was coming from her head instead of the target. It's a minor visual glitch but it's distracting if you're playing seriously. The other gotcha is save file compatibility. If you install a hairstyle mod and then try to load a save that was created on an unmodded ROM, the game will either crash immediately or display corrupted sprites. The reverse is also true. Some mod authors include a save converter, but most don't. You're basically locked into playing fresh once you patch the ROM. If you want to experiment without permanently modifying your main ROM, you can run the patched version through an emulator like DeSmiME or melonDS with a separate save state folder. That way you can test multiple hairstyle packs side by side and roll back instantly if something breaks. I keep about six different ROM variants loaded at any given time across different emulator profiles, each with a different customization mod. It takes up maybe two gigabytes on disk and it's infinitely more convenient than trying to unpatch and repatch the same ROM file repeatedly.
Get the Full Details

The download links tend to rot within a year or two. ROM hack sites reorganize, authors abandon projects, and hosting services shut down. If you're interested in a specific pack, grab the files immediately and store them locally. I maintain a personal archive of every Pokemon ROM hack I've ever installed, organized by game and patch version, because I've lost track of at least three hairstyle mods that were genuinely good and I couldn't find anywhere after the original threads disappeared. There are legitimate limitations to what these mods can do. The DS hardware only supports a certain number of simultaneous color palettes per background, so adding too many custom hairstyles can cause sprite flickering on busy screens. I've seen it happen in areas like Lumiose City's mall interior where the mod adds extra NPC hairstyles on top of the protagonist changes. The game falls back to a reduced palette and everything starts flashing. The fix is usually to disable some of the NPC custom sprites in the patch config, but not all authors provide that option. Another realistic limitation is that you can't mix and match hairstyle mods from different authors without expecting conflicts. Each one modifies overlapping memory addresses, and the patches aren't designed to be layered. If you want to combine a hair mod with a clothing mod, you're better off finding an all-in-one pack or asking the authors to coordinate. I tried building my own combination once by applying two patches sequentially, and the resulting ROM had a 50/50 chance of crashing on the first battle. Deleted it after an hour of troubleshooting.
If you're looking for a starting point, the most reliable packs tend to come from established ROM hacking communities rather than individual uploaders on file-sharing sites. Check the patch notes for ROM version compatibility, MD5 verification steps, and known issues. Those three elements alone will tell you whether an author actually knows what they're doing or if they just threw together some sprite swaps and called it a mod. Installation usually takes between ten and twenty minutes if everything goes smoothly, including emulator setup and ROM verification. If you run into problems, expect to spend another thirty to forty-five minutes diagnosing version mismatches or corrupt patches. The most common failure point is applying a patch to the wrong ROM variant, which is why the checksum verification step isn't optional even though the instructions sometimes make it look like it is. I use BPSTool for .bps patches and xdelta UI for .xdelta files. Both are free and both have been around long enough that they handle edge cases decently. The older IpaIpa or Lobotomy_Tool options work too but they're more finicky with certain patch formats and they don't always report errors clearly, which makes debugging harder when something goes wrong.
Once your patched ROM is running, you can access the hairstyle selection through the normal character customization menu. The mod expands the available options beyond what the base game offers. Some packs add twenty to thirty new hairstyles, while more ambitious ones push toward fifty. The tradeoff is longer load times when switching between outfits and a slightly higher chance of sprite glitches in cutscenes that reference the protagonist's appearance. That's basically how it works. The process is repeatable once you understand the version compatibility requirements and the limitations of the DS hardware. Most people who stick with it end up running a small personal library of patched ROMs for different play sessions, each with a different cosmetic focus. It's not elegant but it's functional and it keeps you from breaking your main install every time you want to try something new.
