Yearn file recognition: distinguish platform formats and disc companion files

English translation of the Chinese original, translated on 2026-10-23. The article body uses automated translation; app descriptions, historical reading notes and video subtitles receive separate editorial checks. Original publication dates, attribution, code and version notes are retained.

Before importing a self-supplied game file into Yearn, understand what it is. A console name in the filename may be unreliable, and extensions are not converters. This article builds a personal file checklist so wrong file selection, missing tracks, and game incompatibility can be investigated separately.

Record the files as originally received

Inspect file information in the system Files app and record the full name, extension, size, and whether it came as one file or a folder. For a long name, open its information panel to confirm the suffix rather than guessing from a thumbnail. Keep a source description in a neighboring text note so the file's purpose is still clear weeks later.

Do not rename or convert yet. Files that work together may reference each other by name, especially disc indexes and tracks. Copy a complete practice set and organize that copy. Renaming is useful organization only when you understand the internal format. Changing zip to gba does not create a runnable handheld game.

Classify single-file formats

Yearn lists NES, SNES, GB/GBC, GBA, N64, NDS, Genesis, and PS1. Common single-file extensions provide initial clues: nes for NES; sfc or smc commonly for SNES; gb and gbc for Game Boy; gba for GBA; nds for NDS; and md or gen commonly for Genesis.

These mappings help selection and inspection; they do not guarantee compatibility for every file with an extension. For a file named Practice Game.gba, expect it in GBA after import. If it appears under an unexpected platform, revisit the source instead of hiding the identification difference with a cover or rename.

The common N64 forms n64, z64, and v64 belong to the same platform. Retain the original extension initially, check whether Yearn recognizes it, then assess runtime. There is no need to rename every suffix uniformly for appearance.

Inspect disc-image files together

PS1 files may use bin, cue, img, iso, pbp, or chd. CUE is particularly easy to misunderstand: it normally describes disc tracks and associated files, so a small size does not mean a small game. A cue of only a few hundred bytes without its referenced tracks cannot usually restore missing data by being imported alone.

Keep a game's companion files together with their original names and letter case. For multiple tracks, read the CUE filenames in a text-capable tool and compare each with the directory. Do not organize by deleting BINs that look duplicated; different tracks may hold data or audio.

Extract archives into inspectable files first

A download or transfer may produce a zip, rar, or 7z container, which is not itself a ROM. Yearn's public platform support does not imply that every archive can be extracted directly. Extract through system file tools or an existing archive utility first, then inspect the actual files.

After extraction, inspect the innermost contents rather than handing the app an outer directory full of notes, screenshots, and duplicate copies. Resolve password, damage, or missing-volume errors in the archive first. Yearn cannot repair a game file that has not been fully extracted. Do not gamble on supposedly universal conversion programs from unfamiliar pages either.

Use a checklist for small-batch import

Create three columns: source filename, expected platform, and import result. Choose three clearly sourced samples from different platforms, import them individually, and record Yearn's category. If one fails, you still know whether the other two succeeded instead of treating one batch as entirely successful or failed.

Watch same-name files on the same platform particularly carefully. Current import behavior places files in the app directory by filename, so reimporting an identical name may replace a copy. Distinguish regions and versions before importing. Renaming CUE-related files also requires updating references, not just one visible filename.

Check file presence separately from successful operation

A library entry after import means the file has at least entered identification. Reaching the title screen, accepting input, and continuing to run are later checks. Record distinct results such as Unrecognized, Visible After Import, Startup Error, and Normal After Title Screen. These are more specific than Will Not Open.

File contents may also help identify an unknown bin or iso. If it is assigned to an unexpected platform, verify the real format at its source rather than insisting based on its extension. Use the dedicated track-file tutorial for complex PS1 images, keeping this article focused on format identification and preparation.

Frequently asked questions

Must manuals and covers in a game folder be imported too? Retain them as your own supporting material, but select only required main files and companion tracks when importing a game. Distinguish images, text, and runnable content.

Can different regional versions of the same game share saves? The title alone cannot determine this. Content version, emulator core, and save type may affect loading. Retain the pairing between the original game file and its saves, then test loading with copies.

The checklist works when you can identify each file's role, expected platform, and companions before import. Even if compatibility problems appear later, you will no longer confuse archives, index files, and complete games.