How to record a full Potato Please run or save a bug clip

Start the recording before starting the shift

For an uncut run, open Steam > Settings > Game Recording, choose Record on Demand and note your start/stop shortcut. Make a short test run and play it back. For the attempt itself, begin recording while the difficulty choice is visible and finish only after the results screen or crash. In the viewer, check that both ends of the footage are present before sending it to anyone. The developer accepts recordings for review and has not published a rule that guarantees reinstatement.

Players discuss uncut recordings for fast hard-difficulty runs ↗

Golden Horn Studios asks for a recording when reviewing a removed time ↗

Valve: recording modes, clips, export and sharing ↗

A long run loses its opening minutes

Background capture keeps a rolling window. Continued play can displace the opening even though the most recent part still plays. Check the retention time and space in the Game Recording settings for Potato Please. For an attempt you want to preserve, use on-demand recording or allow enough space and duration, then save a permanent clip covering the whole run before launching another shift. A clip made after the opening has already disappeared cannot recover it.

Players discuss uncut recordings for fast hard-difficulty runs ↗

Steam Support: recording, timeline gaps, low disk space and the Overlay ↗

Valve: recording modes, clips, export and sharing ↗

Keep a short bug clip alongside the uncut run

After a failure, open the recording timeline and mark a second clip starting just before the triggering input. End it after the incorrect behavior is visible. Save that short selection as its own clip and keep the complete recording separately. For a final-room crash, include the doorway approach and transition, then send the game log too. The log covers the point where the process stopped recording.

Player loses their time when the bunker exit crashes ↗

Studio instructions for a reproducible report, images, video and logs ↗

Steam Support: recording, timeline gaps, low disk space and the Overlay ↗

Export a video another person can play

Open View > Recordings & Screenshots in Steam. Select the game and the saved clip, choose the export-video option and select a destination. Steam’s working recording files use its own timeline format. Play the exported MP4 outside Steam and check both the beginning and the end. That file can accompany a report without requiring the recipient to have your Steam recording directory.

Studio instructions for a reproducible report, images, video and logs ↗

Valve: recording modes, clips, export and sharing ↗

Steam Support: recording, timeline gaps, low disk space and the Overlay ↗

Find a capture made on Steam Deck

On the Deck, open Steam’s main menu and choose Media. Locate the clip by the game and session, preview it and use its sharing menu to send it to your other device if available. On the receiving PC, confirm that it is the correct shift before exporting. Media on the Deck serves the same purpose as View > Recordings & Screenshots in the desktop client.

A player reports how the retail build performed on Steam Deck ↗

Valve: recording modes, clips, export and sharing ↗

Steam Support: recording, timeline gaps, low disk space and the Overlay ↗

Check the audio before sharing a shift

Open Game Recording audio settings before reproducing the bug. Choose audio from the game and leave other applications or the microphone out if their voices are irrelevant. Record a short test with the depot audible, then listen to it before the full run. An uncut run intended for another person should contain only the channels you mean to share.

A creator asks the studio about recording their game and commentary ↗

Valve: recording modes, clips, export and sharing ↗

Steam Support: recording, timeline gaps, low disk space and the Overlay ↗

Use a manual marker for a fault that has no game event

Set a marker shortcut in Steam’s Game Recording settings before reproducing the problem. When the jam becomes visible, press the shortcut once. Open the timeline, find the marker and move the start of the clip back far enough to show the sack or potato entering the machine. A manual marker works even when the game supplies no automatic event for that mechanism.

Studio instructions for a reproducible report, images, video and logs ↗

Valve: recording modes, clips, export and sharing ↗

Steam Support: recording, timeline gaps, low disk space and the Overlay ↗

Steam screenshots and the recording timeline will not open

Try Steam’s Overlay shortcut while the game is running. If Shift+Tab does nothing, check the shortcut in Steam Settings > In Game, the global Overlay switch and the setting under Potato Please Properties > General. Relaunch through Steam after changing them. Open the overlay in a quiet area and make a short test capture. Valve’s normal in-game F12 screenshots also depend on an enabled overlay.

Valve: Steam Community Overlay, Shift+Tab and screenshots ↗

Steam Support: recording, timeline gaps, low disk space and the Overlay ↗

Studio instructions for a reproducible report, images, video and logs ↗

Capture the error window with Windows

Leave the message onscreen and press Windows+Shift+S. Choose Window or Rectangle, capture the error text and save the result from Snipping Tool. Check that the message contains the DLL name or error number, not just the Steam Play button. Add the separate previous-session log when reporting a crash.

Microsoft: Snipping Tool capture, recording and text tools ↗

Potato Please player and developer discussion: How to Report a Bug (please read before posting) ↗

Delay the snip before opening the menu

Open Snipping Tool and choose a delay, then start a new capture. Return to the game and expose the menu or hover state before the delay expires. Select the relevant region when the capture appears and save the image. This helps show the missing Save-button highlight without forcing the menu closed to launch a tool.

Microsoft: Snipping Tool capture, recording and text tools ↗

Potato Please player and developer discussion: How to Report a Bug (please read before posting) ↗

Choose a bounded recording region

On Windows 11 builds with Snipping Tool video recording, open the recording control and choose a rectangle around the game. Start recording, reproduce the menu failure once, stop and review the saved clip. Keep the pointer and the actual button within the selected region; omit conversations and other desktop windows outside it.

Microsoft: Snipping Tool capture, recording and text tools ↗

Potato Please player and developer discussion: How to Report a Bug (please read before posting) ↗

Mark the change and show the result

Valve notes that video can be missing while a game changes resolution or before it signals that it is ready to capture. Record the menu beforehand, make one change and leave enough time to record the new output afterward. Photograph both settings if the transition itself remains absent. A gap by itself does not prove that the game crashed.

Valve: Steam Game Recording support ↗

Potato Please player and developer discussion: Crash as you exit ↗

Replace the expired share link

Steam-hosted clip share links expire after two days. Keep the saved clip locally, generate a fresh link when the developer is ready to inspect it, or export a video for an attachment. Reopen your own link before sending it. Do not delete the only saved clip once a temporary link has been created.

Valve: Steam Game Recording support ↗

Potato Please player and developer discussion: Crash as you exit ↗

Transfer the saved clip before editing

Save the selected clip on the Deck. With the Steam clients signed in and connected, use the clip's send-to-device action and choose the PC as the destination when available. Open it there and export a video if the report needs an attachment. Moving a recording does not transfer the underlying save slot or diagnostic log.

Valve: Steam Game Recording support ↗

Potato Please player and developer discussion: Crash as you exit ↗

Change the recording destination

Open Steam Settings, Game Recording and check which drive stores the recordings. Move the recording folder to a drive with free space or reduce the temporary background recording length or quality. Save any important bug segment before housekeeping. Deleting the game's save folder will not change the recording storage limit.

Valve: Steam Game Recording support ↗

Potato Please player and developer discussion: Crash as you exit ↗

Compare two runs of the same short action

Valve notes that capture performance depends on the hardware and whether hardware encoding is available. Use an already backed-up manual save, the same viewpoint and the same graphics preset. Compare one pass with recording disabled against another with it enabled. Report both results if the drop changes. Avoid comparing a quiet early shift with a fully jammed depot.

Valve: Steam Game Recording support ↗

Potato Please player and developer discussion: Crash as you exit ↗

Pin a short shopping note over the game

Open the Steam overlay, open Notes for Potato Please and write the two next item names and quoted prices from your own terminal. Pin that note and reduce its opacity until you can see the hopper behind it. Return to the game and check that the numbers stay visible before starting the trip. Move it away from a timed letter or unpin it as soon as it blocks a prompt. The notes belong to the Steam game and do not update when your terminal price changes.

Valve: per-game overlay Notes and adjustable pinned windows ↗

MJun.21: equipment prices, prerequisites, letters and Journal task rewards ↗

Keep opposite choices from being compared as one route

Take a screenshot before the choice and another at the route outcome, keeping the correct save slot visible when possible. Make one Steam Note for each branch, paste its own screenshot there, and add the save-slot identifier and exact choice. Reopen each note from the game's Library page and check that the title describes the image below it. Valve supports multiple image-bearing notes per game. They are reference material; reloading the branch still requires a retained game save.

Valve: per-game overlay Notes and adjustable pinned windows ↗

Mark a final scene as a spoiler before making the screenshot public

Take the screenshot with Steam's screenshot shortcut, normally F12, while the ending is on screen. Open the screenshot manager and select just the ending image. In the sharing controls choose the intended audience and mark the potential spoiler before uploading. Give it a neutral caption that names the route without giving away the last sentence. Check the posted item afterward. If you only want the image for your own route notes, keep its local copy and skip the upload.

Valve: Steam Screenshots and the uploader ↗

Player follows the Steam screenshot uploader spoiler control ↗

Capture the crane's on-screen button legend with the Deck shortcut

Hold the Steam button to bring up Valve's shortcut list and locate Take Screenshot. Return to the driving seat so the bottom-left crane legend is visible; use the screenshot combination shown by your Deck before leaving the cab. Open Steam's media or screenshot manager and check that the labels are legible in the saved image. No external F12 key or running video recording is needed. Publishing the image from the manager is a separate choice.

Valve: Steam Deck input test, shortcuts and game-specific layouts ↗

Valve: Steam Screenshots and the uploader ↗

Steam Help & Questions • Raising and lowering the claw ↗

A live viewer saw the bug but you need a clip after the shift

A Steam Broadcast is live. Do not assume the friend who watched the crane jam can retrieve the previous frames from it later. For a reproducible issue turn on Steam Game Recording before the next trial, keep the moment the crane starts moving and the point it stops, and export the clip with your game version. If you only have the live account of what happened, label the report as a description rather than claiming to have footage.

Valve: Steam Broadcasting viewing, invitations and privacy ↗

Steam Support: Broadcasting troubleshooting and desktop handling ↗

Developer: what to include in a Potato Please bug report ↗

A live viewer loses the picture while you check a guide

When you switch from Potato Please to a browser, Steam may display a placeholder if it cannot capture the unfocused game. Refocus the shift and ask the viewer if the depot reappears. If you need to share only gameplay, leave desktop capture off and send the guide link separately. A lost picture during that switch does not show that the depot save failed.

Steam Support: Broadcasting troubleshooting and desktop handling ↗

Potato Please player cannot find the promised multiplayer session ↗

Related field notes

• Replay a finished save and check your leaderboard time
• How to Read Steam Deck Frame Rates Before a Late Shift