Advanced use and troubleshooting
Yearn screenshots: save a game image and organise your records
Save a game image in Yearn, confirm it in Photos, distinguish game captures from system screenshots and keep identifiable progress or troubleshooting records.
On this page
When you reach a special scene or want to report a display problem, use Yearn’s screenshot option to save an image first. A screenshot stores the image visible at that moment and is useful for recording and sharing; you still need a separate save for game progress. Manage the two kinds of files separately so you can find what you need later.
First decide what the screenshot is for
If you are recording a game’s completion, first advance to a point where all the text and characters are fully displayed. If you are reporting a problem, keep a scene that clearly shows the issue instead of cropping it down to a tiny fragment. When comparing the effects of a setting, keep both screenshots on the same screen as closely as possible.
For constantly changing content, open the game’s pause menu before using the screenshot option. Check the saved result to see exactly what the screenshot includes. Save game progress before important actions, and especially avoid repeatedly resetting or exiting the current game just to capture an image. A visual record and a recoverable state serve different purposes.
Save an image from the game menu
Open the pause menu on Yearn’s gameplay screen, find the screenshot option, and use it. Note any completion or error message from the app, then return to the game. If the scene is still changing, first check whether the screenshot captured what you wanted before deciding to retake it. There is no need to press the button repeatedly in quick succession.
A save message indicates that the app ran its screenshot procedure, but you still need to open Photos to confirm the actual result. Device permissions, system state, and whether the image was successfully captured can all affect the final file. Treating ‘tap Screenshot’ and ‘see the saved image’ as two separate steps prevents discovering only when you are ready to share that the file is missing from its expected location.
Check the file and permissions in Photos
Open the system Photos app and check recently added items for the corresponding image. Zoom in to inspect the text and all four edges, making sure it is not a previous frame, a black screen, or an unexpected menu state. If you cannot find it, return to Yearn and look for an explicit error, then check the app’s Photos permissions in system settings.
Depending on the system version, permissions may be under the app’s page in Settings or a privacy-related page. Use the options your system actually provides, then return to Yearn and take an easily recognizable test image. When a save message appears but no photo can be found, start with this small test instead of repeatedly capturing the same hard-to-distinguish scene.
Distinguish app screenshots from system screen captures
Yearn’s screenshot option saves the game image. An iPhone or iPad system screen capture records what is currently displayed on the device screen and may include controls, menus, and system interface elements. Try the app’s option first for a clean game image. To show a button’s location or an error message, a system screen capture is usually more direct.
The two methods may produce images with different dimensions and contents, so identify which type of file each is before comparing them. Do not use a system screen capture cropped in Photos to judge whether an original game screenshot is missing its edges. Keep the originals and make copies for sharing to simplify later troubleshooting.
Develop a way to organize your screenshots
Create a game-record album in Photos and organize images by game or purpose. A few clear categories, such as ‘Completion Records,’ ‘Display Comparisons,’ and ‘Issues to Report,’ are easier to maintain than numerous empty albums for individual play sessions. Keep a few images that demonstrate the result, then review and remove the redundant ones.
If you also save an image to Files, you can use the naming pattern ‘game abbreviation_date_purpose.’ For example, ‘示例游戏_20261023_画面边缘’ is a suggested personal filename, not a fixed name automatically generated by the app. Before sharing, check that the image contains no unrelated personal notifications or account information, especially when using system screen captures.
Describe a problem with two images
When reporting a display issue, keep the full screen in the first image; the second can enlarge the specific area. In your written description, include the game’s platform, portrait or landscape orientation, whether you use a physical controller, and what you did just before the issue appeared. The full image supplies context, while the close-up makes text or edges easier to inspect. The combination is usually more effective.
For example, to report a cropped display, first capture a menu at normal proportions, then capture the same menu after changing the scaling and point out which line is missing. Do not send only an enlarged detail and leave the recipient to guess what should have been there. For audio or input-lag issues, a still image can show only the interface state; also describe the action and result in words.
Common questions and checks after saving
Can a screenshot restore a game? No. A screenshot is an image and does not contain the full state required for the emulator to continue running. Before exiting or switching devices, make a separate in-game save or save state and check that you can load it using the corresponding tutorial.
What if the app says it saved an image but there is nothing in Photos? First check Photos permissions and recently added items, then test again with a clear, still image. The app’s internal files and the system photo library are separate locations. If necessary, use a supported file-sharing procedure to inspect the app’s documents, but do not delete the app as a way of looking for images.
After taking a screenshot, confirm that it opens in the expected location, shows the complete content, and has a clear purpose. When sending it, select the correct original or sharing copy and keep your own record afterward. The next time a similar problem occurs, you can compare what changed without having to recall the settings from memory.
Related tutorials and sources
Preserve progress with a save, Record launch problems.
Information checked on October 23, 2026. Public release information comes from the Yearn store page and Apple’s lookup API, is 1.0.2, requiring iOS / iPadOS 17 or later. Follow the version actually shown on the device.