How to Install hShop on Your 3DS: A Complete Setup Guide

hShop is one of the most popular third-party content repositories for the Nintendo 3DS, offering a massive library of games, DLC, updates, and system titles — all accessible directly from your handheld. But before you can use it, your 3DS needs to meet some prerequisites, and the installation process has a few steps that trip people up if they're not expecting them.

Here's what you need to know before you start.

What Is hShop and How Does It Work?

hShop is a web-based and CIA-installable shop for homebrew-enabled 3DS systems. It works by delivering .cia files — a Nintendo-native format for installable titles — directly to your device over Wi-Fi. Think of it as an unofficial storefront that indexes and serves content to 3DS systems running custom firmware (CFW).

Unlike physical cartridges or the official Nintendo eShop (which has since shut down), hShop operates entirely through your console's homebrew infrastructure. You browse, queue, and install titles without ever touching a computer after the initial setup.

The Non-Negotiable Prerequisite: Custom Firmware

🔧 hShop will not work on an unmodified 3DS. Full stop.

To install and use hShop, your console must already be running Luma3DS — the most widely used custom firmware for the 3DS family. Luma3DS is typically installed alongside boot9strap, which is the foundational exploit that gives CFW persistent access to your system.

If your 3DS isn't already running custom firmware, you'll need to complete that process first via a guide like the one at 3ds.hacks.guide. The hShop installation assumes CFW is already in place.

Supported hardware includes:

  • Nintendo 3DS, 3DS XL, 2DS
  • Nintendo New 3DS, New 3DS XL, New 2DS XL

The process is largely the same across these models, though some steps vary slightly depending on system version and exploit path.

What You'll Need Before Installing hShop

RequirementDetails
Custom firmwareLuma3DS with boot9strap
FBI installedThe CIA installer homebrew app
SD cardSufficient free space (varies by content)
Wi-Fi connectionRequired for browsing and downloading
System versionGenerally 11.x — CFW handles the rest

FBI is the key tool here. It's a homebrew application that can install .cia files, and it's how you'll get hShop onto your 3DS in the first place.

Step-by-Step: Installing hShop on Your 3DS

Step 1 — Open FBI on Your 3DS

Launch FBI from your homebrew launcher or directly from your home menu if it's already installed as a CIA title. FBI is the gateway for everything that follows.

Step 2 — Navigate to the QR Code Scanner

Inside FBI, select Remote Install, then choose Scan QR Code. Point your 3DS camera at the hShop QR code, which is available on the official hShop website (hshop.erista.me). This QR code contains the direct URL to the hShop .cia installer file.

Step 3 — Install the hShop CIA

FBI will download and install the hShop application directly to your system. This installs hShop as a title on your home menu, meaning you can launch it like any other app going forward.

Step 4 — Launch hShop and Create an Account

Open hShop from your home menu. On first launch, you'll be prompted to either create a free hShop account or browse as a guest. An account lets you maintain a download queue and track your library across sessions — guest access is more limited.

Step 5 — Browse, Queue, and Install

Once inside hShop, you can search by title, browse by category, or filter by region. When you select a title, hShop downloads and installs it directly to your SD card or system memory. Larger titles — especially those with multiple language tracks or DLC bundles — can take significant time depending on your Wi-Fi speed.

Factors That Affect Your Experience 🎮

Not everyone's hShop setup will behave identically. Several variables meaningfully change how smooth or complicated the process is:

SD card speed and size — hShop installs titles as .cia files, which can be several gigabytes for larger games. A slow or nearly-full SD card will bottleneck downloads and may cause install errors.

Wi-Fi stability — The 3DS uses 2.4 GHz Wi-Fi only and doesn't support 5 GHz networks. A weak or congested signal will cause slow downloads or timeouts mid-install.

System memory vs. SD card installation — By default, most titles install to the SD card. System memory (NAND) is limited and generally not recommended for large installs.

New 3DS vs. original 3DS hardware — The New 3DS models have faster processors and more RAM, which makes navigating hShop's interface noticeably snappier. On original 3DS hardware, the browser can feel sluggish when loading large category pages.

FBI version — An outdated FBI build can cause QR scanning failures or installation errors. If the QR method doesn't work, FBI also supports direct URL entry under the same Remote Install menu.

Common Installation Problems

QR code won't scan — Lighting and camera distance matter. Try in a well-lit room with the QR code displayed on a bright monitor screen at about 20–30 cm distance.

"Error" during CIA install — Usually points to a full or corrupted SD card. Check available space and run an error check on the card from a computer.

hShop won't connect after install — Confirm your Wi-Fi credentials are saved in System Settings and that your network is 2.4 GHz compatible.

Download stalls at a percentage — This is often a server-side issue or a Wi-Fi dropout. hShop allows you to resume queued downloads in most cases.

The Variables That Make Each Setup Different

The mechanical steps above are consistent across most CFW-enabled 3DS systems — but how smoothly this goes, and what you can realistically install and enjoy, depends on factors specific to your situation: your hardware model, your SD card capacity, the stability of your home network, and how your CFW was originally configured.

Some users hit every step cleanly in under ten minutes. Others run into SD card issues, Wi-Fi compatibility quirks, or FBI versioning problems that require a bit of troubleshooting. Whether hShop becomes a seamless part of your 3DS experience or a project with a few extra steps really comes down to the specifics of your own setup.