Import PS1 disc images into Yearn: CUE, BIN and multiple tracks

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.

PS1 images often consist of several files. If you see a small CUE and a large BIN, retain them as one set before choosing the launch entry point. Organizing companion relationships before import is more useful than repeatedly changing extensions after a black screen.

Keep the complete original folder first

Prepare a game image you lawfully possess and are entitled to use. Create a separate directory in Files and keep every file from the same disc together. Make an import copy while retaining the unchanged original. Include the game name and disc number in the directory name so multi-disc files do not become mixed.

Confirm that files have fully downloaded to the device. Cloud filenames do not mean large track files are local. Check sizes after downloading. For an archive, extract it with a supported tool and inspect its real contents. Yearn identifies game files; an arbitrary archive is not necessarily a directly runnable image.

Distinguish CUE and BIN roles

A CUE is usually text describing track-to-file relationships, while a BIN may hold actual disc data. A tiny CUE without its referenced tracks is not a complete game. Conversely, one BIN may not retain all track information for a disc, especially a title with audio tracks.

Use a plain-text reader to inspect your CUE copy, focusing on referenced filenames. Compare spelling, extensions, spaces, and disc numbers with the actual files beside it. Reading requires no changes to track types or addresses. If those fields are unfamiliar, keep the original contents and return to completeness checks.

Start importing with a simple single-track pair

For the first check, choose a clearly sourced simple CUE/BIN pair already sharing a base name. In Yearn's Add flow, select file import and select the related files together. Inspect platform and name in the library afterward, then try launching. Retain the original folder for preparing another copy if needed.

Matching names are only a common convention; actual references follow the CUE contents. Do not rename files just to make names match and forget the references. Do not import only the smallest file and assume every other track copied too. Verify through complete startup, reading, and sound behavior.

Multi-track images need extra checks

If the directory has several Track-numbered BINs, count them and compare the CUE references. Keep every related file in one working directory rather than selecting only the first data track. Yearn's import handling may vary across companion structures. Judge complex multi-track content by actual import results in the current version.

For a title screen without music, check missing audio tracks or references that cannot find files. This differs from unreadable main data. Record the scene where content is missing instead of immediately changing the extension. Renaming a suffix neither restores lost tracks nor converts the image format.

Separate BIOS issues from image issues

PS1 startup may also need suitable BIOS files. Check BIOS status in Yearn's settings and follow the relevant tutorial for files you are entitled to use. Missing BIOS and missing disc tracks are different problems: one concerns system files, the other disc material. They cannot substitute for one another.

If another PS1 game runs and only this image fails, prioritize this set's completeness and format. If all PS1 games fail while other consoles work, focus on PS1 BIOS and platform requirements. This comparison reduces unnecessary reimports.

Avoid same-name overwriting and multi-disc confusion

Before importing, check for an existing same-name file in the library. Back up important progress and clarify your goal before reimporting a corrected image. Identical names may cause replacement. Repeated import is not version management that automatically retains every historical copy.

Retain clear Disc numbers and separate companion relationships for multi-disc works. This tutorial covers file preparation and one image's runtime check only. Confirm an appropriate mid-game disc-switching entry point in the actual version. Verify the first disc before relying on the title for long-term play.

Questions and final checks

The list shows similar CUE and BIN entries. Which should I delete? First identify the actual file and startup behavior behind each entry, then address duplicate display. Do not delete one merely because of size or name; the other may still depend on it. Keep a complete external copy before organizing so restoration is easier.

Does CHD or PBP support mean every such file runs? An extension describes a container or format class. Internal content, creation method, and platform compatibility still affect results. Confirm that the file belongs to the target platform rather than treating a format list as a guarantee for every game.

Finally, check the title screen, game start, scene transitions, and sound, covering an actual disc-read operation where possible. Record the file list, platform, BIOS status, and failure point together. For feedback, these facts and screenshots without private paths are sufficient; you need not upload game content or personal storage addresses.