emumovies.com No paid content found

LaunchBox artwork is the set of images and videos that LaunchBox displays alongside each game in your library — box fronts, clear logos, screenshots, backgrounds, and gameplay video snaps. You get it either by scraping from within LaunchBox or by downloading packs from a source like EmuMovies, then letting LaunchBox associate those files with the correct games. The main condition to keep in mind: artwork only shows up reliably when the file names and folder structure match what LaunchBox expects for that platform.

The types of LaunchBox artwork

LaunchBox separates artwork by role, and each role appears in a different part of the interface:

EmuMovies describes its library as covering "Boxart, Covers, Videos, Snapshots and Scraping Data" across handheld, console, and computer systems, and its download entries list availability as "Site, FTP & Sync" — meaning the same pack can be pulled through the website, an FTP connection, or a sync tool rather than only one route.

How to get artwork

Two practical paths:

Scrape inside LaunchBox. LaunchBox has a built-in metadata and media downloader. Point it at your platform, choose which media types you want, and it fetches images from its own database. This is the fastest route for common systems and needs no manual file handling.

Download packs and sync them. For complete, curated sets — the kind EmuMovies hosts — you download a pack and then make LaunchBox aware of it. EmuMovies packs are organized per system and per media type, for example a "Sony Playstation 2 Backgrounds Pack" or a "Microsoft MSX Boxes-2D Pack," each with a file list. Some packs are split by quality: an Xbox 360 video snap pack, for instance, is offered at HD 1080p, HQ 480p, and SQ 240p, with different availability per tier.

A middle option is the sync route: EmuMovies lists "Sync" as an availability method, which means a tool handles the transfer instead of you downloading and unzipping manually.

Importing and associating artwork

The goal is to end up with files named after your ROMs and placed in the folders LaunchBox reads.

1. Confirm your ROM file names. LaunchBox matches media to games by name. If your ROM is Sonic The Hedgehog (USA).zip, the artwork file generally needs the same base name.
2. Place files in the platform's media folders. LaunchBox keeps images under its Images directory, split by platform and then by media type (Box - Front, Clear Logo, and so on). Video snaps go under the Videos directory, also per platform.
3. Refresh the view. After adding files, restart LaunchBox or refresh the platform so it re-reads the folders.
4. Verify per game. Select a game and check the details pane — if the box front and logo appear, the association worked.

If you downloaded a pack with its own folder layout, keep that layout intact rather than flattening everything into one folder; the media-type subfolders are what tell LaunchBox which image is a box front versus a clear logo.

When artwork doesn't show

• Name mismatch. The most common cause. Compare the ROM name to the image file name character by character, including region tags and parentheses.
• Wrong platform folder. A Genesis box art file dropped into the NES platform folder won't appear.
• Wrong media subfolder. A clear logo sitting in the Box - Front folder may not render where you expect.
• Video codec or resolution. Some video snap packs are offered in specific resolutions and formats; a clip that doesn't play may be a format the frontend can't decode rather than a naming problem.
• Partial sets. Community packs are often incomplete by design. A pack may cover a system's retail run but exclude, say, a peripheral's games — one Xbox 360 video snap set explicitly notes that no Kinect games are included.

LaunchBox artwork vs. HyperSpin artwork

They overlap in content but differ in packaging. HyperSpin artwork is built around that frontend's theme and wheel structure, while LaunchBox organizes media by platform and media type. Because both ultimately store images and videos as files, the same source packs (EmuMovies hosts both "hyperspin artwork" and "launchbox artwork") can often be reused — but you should expect to rename files and move them into LaunchBox's folder scheme rather than dropping a HyperSpin set in unchanged. Treat cross-use as a conversion task, not a copy-paste.

Choosing an approach

• Small or common library: scrape inside LaunchBox. Least effort, good coverage.
• Large or curated library: download complete packs and sync them. More control over accuracy, more setup work.
• Mixed: scrape for metadata, then layer in downloaded packs for the systems where you want box-accurate or high-quality video media.

Whichever you pick, the deciding factor is naming consistency — get that right and the rest of the artwork pipeline falls into place.

Video snaps are short gameplay preview clips that emulation frontends play when you highlight a game in your library. Instead of a static box art image, the frontend shows a few seconds of actual gameplay, which makes browsing a large collection faster and more visual. They are used in frontends such as LaunchBox, Hyperspin, RetroPie, and GameEx, and are typically distributed as per-system media packs rather than individual files. If you are building or cleaning up a frontend library and want moving previews instead of still images, video snaps are the relevant media type.

What a video snap actually contains

A video snap is a brief capture of a game running, usually trimmed to a representative moment rather than a full playthrough. In the EmuMovies catalog, packs are organized by system and by naming convention, for example a "Microsoft XBOX 360 Video Snaps Pack (XBLA)" with a file list tied to a No-Intro naming set. That naming matters: frontends match media to ROMs by filename, so a snap pack built against No-Intro names will line up cleanly with a No-Intro ROM set.

Some snaps are platform-level rather than game-level. The catalog lists items like "Colecovision Platform Video," "Neo Geo CD Platform Video," and "Microsoft XBOX Platform Video," which are used as system intro or menu videos rather than per-game previews.

Quality tiers and what they mean

EmuMovies distributes video snaps in multiple quality tiers, and the same XBLA pack is offered at three levels:

The trade-off is storage and playback load versus sharpness. A 240p snap looks fine in a small preview box but degrades if scaled up; a 1080p set is much larger on disk and needs more decoding power. Pick the tier that matches your display size and hardware, not the highest available.

How snaps get into your frontend

The general flow is the same across frontends:

1. Get the media pack for your system in the quality tier you want.
2. Place the files in the frontend's video/media folder for that platform, following the frontend's expected folder structure.
3. Match by filename — the snap filename must correspond to the ROM or game entry name.
4. Run the scraper or media import so the frontend links each game to its video.
5. Verify by highlighting a game and confirming the preview plays.

EmuMovies states availability through three channels: Site, FTP & Sync. In practice that means you can download packs directly from the site, pull them over FTP, or use a sync tool that keeps your local media aligned with the collection. The sync route is the one to use if you are maintaining a large multi-system library and do not want to re-download packs by hand.

Scraping tools are the other half of the equation. Frontends like LaunchBox, Hyperspin, and RetroPie scrape metadata and media, and video snaps are one of the media categories those tools can fetch or import. The catalog keywords reflect this directly: hyperspin scraping, launchbox scraping, and retropie scraping all sit alongside the video snap packs.

Where snaps come from and how packs are credited

EmuMovies is a web archive for videogame artwork, box art, covers, videos, snapshots, and scraping data across handheld, console, and computer systems. Individual packs are often uploaded and credited to specific contributors — the XBLA video snaps pack, for example, credits its captures and edits to named users and notes it was a "second pass" where everything that ran was recorded, with no Kinect games included. That kind of note is worth reading before you download, because it tells you the coverage boundaries of the set.

Common use cases

• Menu previews — the primary use: a moving clip in the game-selection screen.
• Attract mode — cycling through snaps automatically when the frontend is idle.
• Collection organization — because snaps are named to match ROM sets, they double as a consistency check on whether your ROM naming is clean.
• Platform intros — system-level videos used as transitions when entering a platform.

Practical notes before you download

• Check the file list attached to a pack to confirm it matches your ROM naming convention.
• Confirm the quality tier against your hardware and storage.
• Decide whether you want site download, FTP, or sync based on how many systems you maintain.
• Read the pack description for coverage caveats (missing categories, second-pass notes, mature content flags).

If your goal is a frontend that shows gameplay instead of static art, video snaps are the media type to collect, and matching the tier and naming convention to your existing setup is what determines whether they just work or need manual fixing.

HyperSpin artwork is the set of image and video files that a HyperSpin frontend displays for each game and system: wheel logos, box art, cartridge and disc images, backgrounds, and theme videos. You get it by downloading media packs that match your game list, then placing each asset type in the folder HyperSpin expects for that system. The main requirement is that file names match your ROM names, because HyperSpin looks up media by name rather than by scanning content.

The main artwork types

HyperSpin themes are built from several distinct asset categories, and each one lives in its own media folder:

• Wheel logos — the horizontal game logos that spin on the wheel. This is the defining HyperSpin visual.
• Box art — front (and sometimes back/spine) cover images for each game.
• Cart art — cartridge label images for cartridge-based systems.
• Disc art — disc images for CD/DVD-based systems.
• Backgrounds — per-system or per-game background images behind the wheel.
• Theme videos — animated backgrounds and transitions used by themes.

EmuMovies organizes its library along these same lines. Its download listings include, for example, a "Sony Playstation 2 Backgrounds Pack," a "Microsoft MSX Boxes-2D Pack," and a "Sega Genesis - Complete, Accurate USA Retail Box Art Collection" — each labeled by asset type and system.

Artwork sets vs. video snaps

These are two different media categories, and HyperSpin uses them in different places:

A video snap is a recorded gameplay clip, not a still image. EmuMovies describes its video snaps as "captures & edits" recorded per system — the XBOX 360 XBLA pack, for instance, was recorded in a second pass with everything that ran, and explicitly excludes Kinect games. That kind of note matters: a pack may not cover every title in your list, so expect gaps.

Video snaps also come in quality tiers. The XBOX 360 XBLA pack is listed at three levels — HD 1080p, HQ 480p, and SQ 240p — each with its own file list. Higher tiers cost more storage and bandwidth; 240p is enough for a small preview pane.

Where to source HyperSpin media

EmuMovies is a web archive for videogame artwork, box art, covers, videos, snapshots, and scraping data across handheld, console, and computer systems. Its download listings show three delivery methods for the same pack:

• Site — direct download from the website
• FTP — file transfer from EmuMovies servers
• Sync — a synchronization tool that pulls media to your machine

Availability varies by pack. The PS2 Backgrounds Pack and MSX Boxes-2D Pack list "Site, FTP & Sync." The XBOX 360 XBLA video snaps list all three methods but split by quality tier: HD 1080p via Sync & FTP, HQ 480p via Sync & FTP, and SQ 240p via Site, Sync & FTP. Check the availability line on each pack before planning your download, since not every tier is offered through every method.

Packs are also contributed by individual community members, not only by the site. The Sega Genesis box art collection, for example, was created by a user when the Genesis Mini launched, with covers checked against original print covers plus some customs. Community packs can be excellent, but verify the region and completeness against your own list.

Matching sets to your game list

The most common failure is a name mismatch: the media file is named for a different region, revision, or naming convention than your ROM. To avoid it:

1. Pick a naming convention for your ROMs — No-Intro and ReDump are the common references, and EmuMovies file lists are tagged with them (e.g., "No-Intro," "ReDump").
2. Download the pack that uses the same convention — a No-Intro-tagged media pack pairs with a No-Intro ROM set.
3. Check the region — a "USA Retail Box Art Collection" will not match a European ROM set by name.
4. Compare file lists before downloading — EmuMovies publishes a .txt file list for most packs (e.g., "Microsoft MSX (Boxes-2D)(No-Intro)(EM 2.0).txt") so you can diff it against your game list first.

Folder placement and naming

HyperSpin resolves media by looking in the system's media directory and matching the file name to the game name. The practical rules:

• Each asset type goes in its own subfolder under the system's media folder (wheels, boxes, cart art, disc art, backgrounds, video).
• The media file's base name must equal the ROM's base name, minus the extension.
• Keep the extension the frontend expects for that slot (images vs. video).

Because the exact folder tree depends on your HyperSpin version and theme, confirm the paths against your own installation's media directory rather than assuming a fixed layout. The reliable check is empirical: add one game's media, launch the frontend, and see whether it appears. If it does, the path and name are correct — then batch the rest.

Troubleshooting missing or mismatched artwork

• Nothing shows for a game — the file name does not match the ROM name. Rename the media file to match, or rename the ROM to match the media.
• Some games show, others don't — the pack is incomplete for your list, or covers a different region. Compare the pack's file list against your ROMs.
• Wrong image appears — a region or revision collision; two games share a base name. Separate them by their full No-Intro/ReDump names.
• Video pane is empty but images work — the video snap pack does not include that title, or the video is in a quality tier you did not download.
• Everything is blank — the media folder path is wrong for your setup. Verify against your installation before re-downloading anything.

Start with one system and one asset type (wheel logos are the most visible), confirm it renders, then expand. That sequence isolates naming and path problems before they multiply across a full library.

HyperSpin videos are short gameplay clips — usually called video snaps — that play in the frontend while you browse your game wheel. They are separate from box art, wheel logos, and theme videos, and they live in a per-system media folder that HyperSpin reads by matching each clip's filename to the ROM name. You can source them from a media archive such as EmuMovies, which distributes packs by system and quality tier, then place them in the correct folder and point HyperSpin at that folder.

Video snaps vs. artwork vs. theme videos

These three media types are often confused because they all appear in the same frontend:

A video snap is tied to one game. A theme video is tied to one system. If you drop a theme video into the Video folder, HyperSpin will try to play it as a game clip and it won't match anything.

Where HyperSpin-compatible video packs come from

EmuMovies is a web archive for videogame artwork, box art, covers, videos, snapshots, and scraping data across handheld, console, and computer systems. Its download listings show packs organized per system and per media type, with availability noted as Site, FTP & Sync — meaning the same pack can be pulled through the website, an FTP connection, or a sync tool.

Video snap packs are typically published in multiple quality tiers. For example, the Microsoft XBOX 360 (XBLA) Video Snaps Pack is listed in three versions:

• HD 1080p — Sync & FTP
• HQ 480p — Sync & FTP
• SQ 240p — Site, Sync & FTP

That tiering matters for HyperSpin because higher resolutions mean larger files and more disk space, while lower resolutions load faster on weaker hardware. The same listing notes the pack was recorded in a second pass with everything that ran captured, and that no Kinect games are included — a useful reminder that a pack's coverage is defined by what the uploader recorded, not by the full system library.

Packs are also versioned and include a file list, e.g. Microsoft XBOX 360 XBLA (Video Snaps)(HD)(No-Intro)(EM 1.1).txt. The (No-Intro) tag tells you which ROM naming set the filenames follow, and EM 1.1 is the EmuMovies set version. Matching your ROM set to the same naming convention is what makes the clips appear automatically.

How video snaps are named and organized

HyperSpin matches media by filename, so the clip name must equal the ROM name (minus extension). The standard layout is:

HyperSpin\
  Media\
    Sega Genesis\
      Video\
        Sonic the Hedgehog (USA).mp4
      Box Art\
      Wheel\
      Backgrounds\
    Nintendo Entertainment System\
      Video\
        Super Mario Bros. (World).mp4

If your ROM is Sonic the Hedgehog (USA).md and your clip is Sonic The Hedgehog (USA).mp4, the capitalization difference can break the match on some setups. Keep region tags, revision tags, and punctuation identical between the two.

Steps to enable videos in HyperSpin

1. Confirm your ROM naming set. Check whether your ROMs follow No-Intro, Redump, or another convention. Download the matching video pack version so filenames line up.
2. Download the pack through the site, FTP, or sync option listed on the pack page. Sync is usually the least error-prone because it places files in the expected structure.
3. Extract into the system's Video folder under Media\[System]\. Do not flatten multiple systems into one folder.
4. Verify a sample. Pick two or three games you know are in the pack and confirm the filenames match your ROMs exactly.
5. Set the video path in HyperSpin's settings for that system so it points at Media\[System]\Video\.
6. Launch HyperSpin and scroll the wheel. The clip should start after the wheel settles on a game. If nothing plays, the mismatch is almost always in step 4.

Common problems and how to troubleshoot them

• No video for some games. The pack doesn't cover every title. Check the pack's file list before assuming something is broken.
• Video plays for the wrong game. Two ROMs share a similar name, or a filename was edited. Rename the clip to match the ROM exactly.
• Video never plays at all. The path in settings points at the wrong folder, or the folder is named differently from the system name in HyperSpin.
• Stuttering or slow loading. You're using HD 1080p clips on hardware that can't decode them smoothly. Switch to the HQ 480p or SQ 240p version of the same pack.
• Clips from a different ROM set don't match. A Redump-named pack won't line up with No-Intro ROMs. Use the pack built for your naming convention, or rename one side to match.

The short version: pick the video pack that matches your ROM naming set, extract it into Media\[System]\Video\, confirm filenames match, and point HyperSpin at that folder. Most "missing video" complaints trace back to a naming mismatch rather than a missing file.

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:

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.

1. 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.
2. Download the matching tier and file list for your system.
3. Place the videos in the frontend's video/media directory, or import them through the frontend's media manager.
4. Run a scrape or sync so the frontend associates each clip with the right game entry.
5. 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.