What Are Gameplay Videos (Video Snaps) and How Do You Use Them in Emulation Frontends?
Gameplay videos, commonly called video snaps, are short clips that show a game actually running — usually 10–30 seconds of attract mode or live gameplay, sometimes with title/theme overlays. In an emulation frontend, they play in the preview pane when you highlight a game, replacing or supplementing static box art. You use them by downloading a pack that matches your system and region set, then placing the files where your frontend expects them (or letting a scraper/sync tool fetch them). The main practical decisions are resolution tier (SQ 240p, HQ 480p, HD 1080p) and delivery method (site download, FTP, or sync).
Video snaps vs. other media types
Emulation media libraries mix several asset categories, and they are not interchangeable:
| Media type | What it is | Where it appears |
|---|---|---|
| Video snaps | Short gameplay/attract clips per game | Game preview pane, wheel transitions |
| Platform videos | One themed clip per console/system | System selection screen |
| Box art (2D/3D) | Cover scans, front/spine art | Game list, grid, carousel |
| Backgrounds | Full-screen art behind the UI | Behind menus and lists |
| Logos / carts / discs | Small identifying graphics | Wheel art, labels |
A "platform video" (e.g., a Neo Geo CD or PlayStation 3 platform clip) is a single system-level intro, not a per-game snap. If your wheel shows a system animation but no per-game preview, you have platform videos but are missing video snaps.
Resolution tiers and when to choose each
Packs on EmuMovies are distributed in tiers. The XBOX 360 XBLA Video Snaps Pack, for example, is listed with three availability lines: HD 1080p, HQ 480p, and SQ 240p, each with its own sync/FTP/site option and file list.
- SQ 240p — smallest files, fastest to sync, lightest on storage and GPU. Good for low-power handhelds, Raspberry Pi-class devices, or large libraries where you want everything covered.
- HQ 480p — middle ground. Reasonable file size, visibly better on a TV or monitor than 240p.
- HD 1080p — largest files, sharpest on big screens. Best for a desktop/HTPC build with ample disk space and a wired or fast connection.
Choose the highest tier your storage and playback hardware handle smoothly; if previews stutter or sync takes too long, step down a tier rather than mixing tiers inconsistently.
How to obtain packs
EmuMovies lists three availability channels on its packs, and they are not the same thing:
- Site — direct download from the site.
- FTP — bulk transfer, useful for large multi-system collections.
- Sync — a sync tool that pulls and updates files for you.
Each pack page also publishes a file list (e.g., Microsoft XBOX 360 XBLA (Video Snaps)(HD)(No-Intro)(EM 1.1).txt). Download the file list first and compare it against your ROM set — the naming inside it tells you exactly which games the pack covers, so you can spot gaps before committing to a large download.
Note that coverage is set-specific. The XBLA pack, for instance, states it was a second pass where "everything that ran was recorded" and that no Kinect games are included. Expect similar caveats on other packs.
Adding video snaps to LaunchBox, Hyperspin, and RetroPie
The general pattern is the same everywhere: get files named to match your ROMs, then point the frontend at the folder.
- Confirm your ROM naming. Packs are built against known sets (No-Intro, Redump, etc.). If your ROMs use a different naming scheme, previews will not match.
- Download the matching tier and file list for your system.
- Place the videos in the frontend's video/media directory, or import them through the frontend's media manager.
- Run a scrape or sync so the frontend associates each clip with the right game entry.
- Verify by highlighting a few games and checking that the correct clip plays.
For LaunchBox, media is organized per-platform; import the video folder for that platform and let it match by game title. For Hyperspin, videos live in the system's media folder and are matched by ROM name, so exact naming matters most here. For RetroPie, scraping pulls media into the gamelist; you can also drop files into the system's media directory and reference them in the gamelist XML.
Naming conventions and file-list matching
This is where most failures originate. The frontend matches a video to a game by filename, so the video's name must equal the ROM's name (minus extension) under the frontend's expected convention. Use the pack's published file list as the source of truth:
- If a game is in your ROM set but not in the file list, that pack simply does not cover it.
- If a game is in the file list but the filename differs from your ROM, rename one side to match.
- Keep the same naming scheme across a system; mixing No-Intro and non-No-Intro names creates partial matches.
Troubleshooting
Videos don't show at all
- Wrong folder, or the frontend hasn't been told to use that media path.
- Filename mismatch between video and ROM.
- The game isn't in the pack's file list.
Wrong resolution or quality looks off
- You downloaded a different tier than intended — check the file list suffix (HD/HQ/SQ).
- Mixed tiers in one folder can make quality look inconsistent.
Missing entries
- Coverage gaps are normal; check the file list for the specific system and set.
- Region or set mismatches (e.g., a USA-only pack against a mixed-region ROM set) leave holes.
Playback stutters
- Step down a tier (1080p → 480p → 240p) or move storage to a faster drive.
The reliable workflow is: pick the tier your hardware handles, download the file list, match names to your ROM set, then sync or import and verify a sample before doing the whole library.