uConsole RetroPie ROM Transfer: SFTP, Samba, and USB — Which Works Best for Beginners?

The easiest way: SFTP, not Samba

If you’ve been fighting Samba errors, stop. SFTP does the same job with almost no setup, and since SSH is enabled by default on most Raspberry Pi images — including the uConsole RetroPie build — you’re already most of the way there.

SFTP is file transfer layered on top of SSH. Any program that speaks SSH can move files to and from your uConsole without touching Samba at all.

FileZilla: the quickest path to dragging ROMs over

FileZilla is free, runs on Windows, Mac, and Linux, and needs zero configuration on the uConsole side. Open it and fill in the Quickconnect bar at the top:

• Host: your uConsole’s local IP address
• Username: pi (the default on Raspberry Pi images)
• Password: whatever you set during setup — often raspberry on a fresh image, though you should change that if you haven’t
• Port: 22

Hit Quickconnect. On the right panel, navigate to /home/pi/RetroPie/roms/ and open the subfolder for the system you want — snes, gba, nes, and so on. On the left panel, find your ROM files on the PC. Drag them across. That’s it.

If you don’t know your uConsole’s IP address yet: connect a keyboard and run hostname -I in a terminal, or check the connected-devices list in your router’s admin page.

WinSCP: the Windows-native alternative

WinSCP is Windows-only but feels more like File Explorer than FileZilla does. On first launch, choose SFTP as the protocol, then enter the same IP, username, password, and port 22. The two-panel interface makes it straightforward to drag files between your PC and the uConsole’s ROM folders. Either tool works — pick whichever interface you like.

Making Samba work if you want it

Samba is genuinely useful once it’s running, because the ROM folders appear as a permanent network drive in Windows Explorer and you can access them without opening a separate app. The trouble is setup is fiddly, and the most common failure point is an SMB version mismatch: Windows 10 and 11 have SMB1 disabled by default, and older Samba configs still try to use it.

The cleaner path is to use RetroPie’s own Samba installer rather than setting it up manually. From the main RetroPie screen, go to the RetroPie menu, then RetroPie Setup, then Configuration / tools, then samba, and run the install from there. After a reboot, type \\[your-uconsole-IP]\roms directly into the Windows Explorer address bar. Accessing by IP is more reliable than by hostname.

If it still doesn’t appear, confirm that the uConsole and your PC are on the same network and same subnet — it’s a surprisingly common gotcha when a PC is on a wired connection and the uConsole is on Wi-Fi with slightly different router settings.

USB drive: the zero-configuration fallback

No networking required at all. Format a USB drive as FAT32, copy your ROMs onto it, plug it into the uConsole, and move the files into /home/pi/RetroPie/roms/[system]/. RetroPie also has a USB ROM Service option under RetroPie Setup that syncs files automatically each time you plug the drive in — worth enabling if you plan to add ROMs regularly and don’t want to manually copy every time.

What PuTTY actually does (and doesn’t do)

PuTTY is an SSH terminal. You can use it to run commands on the uConsole — useful for things like updating packages or editing config files — but it doesn’t transfer files by itself. If you want to use a command-line approach for file transfer, look at scp or rsync instead. For most beginners, FileZilla is easier.

Quick comparison

• FileZilla or WinSCP over SFTP: easiest to set up, works immediately, good for regular transfers
• Samba: convenient as a permanent network share, harder to configure, worth it if you want Windows Explorer access
• USB drive: no networking required, slightly more manual effort per session
• PuTTY: SSH terminal only — not a file transfer tool on its own

One thing worth sorting out early: a static IP

If your router assigns addresses via DHCP, the uConsole’s IP can change after a reboot and suddenly FileZilla can’t connect. Set a static DHCP lease in your router’s settings by tying a fixed IP to the uConsole’s MAC address. Most router admin pages have this under something like “Reserved IP” or “Address Reservation.” Once that’s done, every method above will always point to the same address without you having to look it up again.