uloop-screenshot
uloop screenshot
Take a screenshot of any Unity EditorWindow by name and save as PNG.
Usage
uloop screenshot [--window-name <name>] [--resolution-scale <scale>] [--match-mode <mode>] [--capture-mode <mode>] [--annotate-elements] [--elements-only] [--output-directory <path>]
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
--window-name |
string | Game |
Window name to capture. Ignored when --capture-mode rendering. |
--resolution-scale |
number | 1.0 |
Resolution scale (0.1 to 1.0) |
--match-mode |
enum | exact |
Window name matching mode: exact, prefix, or contains. Ignored when --capture-mode rendering. |
--capture-mode |
enum | window |
window=capture EditorWindow including toolbar, rendering=capture game rendering only (PlayMode required, coordinates match simulate-mouse) |
--output-directory |
string | "" |
Output directory path for saving screenshots. When empty, uses default path (.uloop/outputs/Screenshots/). Accepts absolute paths. |
--annotate-elements |
boolean | false |
Annotate interactive UI elements with index labels (A, B, C...) on the screenshot. Only works with --capture-mode rendering in PlayMode. |
--elements-only |
boolean | false |
Return only annotated element JSON without capturing a screenshot image. Requires --annotate-elements and --capture-mode rendering in PlayMode. |
Match Modes
| Mode | Description | Example |
|---|---|---|
exact |
Window name must match exactly (case-insensitive) | "Project" matches "Project" only |
prefix |
Window name must start with the input | "Project" matches "Project" and "Project Settings" |
contains |
Window name must contain the input anywhere | "set" matches "Project Settings" |
Window Name
The window name is the text displayed in the window's title bar (tab). Common names: Game, Scene, Console, Inspector, Project, Hierarchy, Animation, Animator, Profiler. Custom EditorWindow titles are also supported.
Global Options
| Option | Description |
|---|---|
--project-path <path> |
Optional. Use only when the target Unity project is not the current directory. |
Examples
# Take a screenshot of Game View (default)
uloop screenshot
# Capture game rendering (coordinates match simulate-mouse, PlayMode required)
uloop screenshot --capture-mode rendering
# Annotate interactive UI elements with index labels (for simulate-mouse workflow)
uloop screenshot --capture-mode rendering --annotate-elements
# Get UI element coordinates without capturing an image (fastest)
uloop screenshot --capture-mode rendering --annotate-elements --elements-only
# Take a screenshot of Scene View
uloop screenshot --window-name Scene
# Capture all windows starting with "Project" (prefix match)
uloop screenshot --window-name Project --match-mode prefix
# Save screenshot to a specific directory
uloop screenshot --output-directory /tmp/screenshots
# Combine options
uloop screenshot --window-name Scene --resolution-scale 0.5 --output-directory /tmp/screenshots
Output
Returns JSON with:
ScreenshotCount: Number of windows capturedScreenshots: Array of screenshot info, each containing:ImagePath: Absolute path to the saved PNG file. Empty when--elements-onlyis used because no image file is written.FileSizeBytes: Size of the saved file in bytesWidth: Captured image width in pixelsHeight: Captured image height in pixelsCoordinateSystem:"gameView"(image pixel coords that must be converted withResolutionScaleandYOffsetbefore using withsimulate-mouse) or"window"(EditorWindow capture)ResolutionScale: Resolution scale used for captureYOffset: Y offset used insim_y = image_y / ResolutionScale + YOffsetwhenCoordinateSystemis"gameView"AnnotatedElements: Array of annotated UI element metadata. Empty unless--annotate-elementsis used. Sorted by z-order (frontmost first). Each item contains:Label: Index label shown on the screenshot (A=frontmost,B=next, ...)Name: Element nameType: Element type (Button,Toggle,Slider,Dropdown,InputField,Scrollbar,Draggable,DropTarget,Selectable)SimX,SimY: Center position in simulate-mouse coordinates (use directly with--xand--y)BoundsMinX,BoundsMinY,BoundsMaxX,BoundsMaxY: Bounding box in simulate-mouse coordinatesSortingOrder: Canvas sorting order (higher = in front)SiblingIndex: Transform sibling index under the element's direct parent (not a reliable z-order signal across nested UI hierarchies)
Coordinate Conversion (gameView)
When CoordinateSystem is "gameView", convert image pixel coordinates to simulate-mouse coordinates:
sim_x = image_x / ResolutionScale
sim_y = image_y / ResolutionScale + YOffset
When ResolutionScale is 1.0, this simplifies to sim_x = image_x, sim_y = image_y + YOffset.
When multiple windows match (e.g., multiple Inspector windows or when using contains mode), all matching windows are captured with numbered filenames (e.g., Inspector_1_*.png, Inspector_2_*.png).
Notes
- Use
uloop focus-windowfirst if needed - Target window must be open in Unity Editor
- Window name matching is always case-insensitive
More from hatayama/uloopmcp
uloop-find-game-objects
Use first when the user asks about the currently selected GameObject in the Unity Hierarchy. Inspect selected object details with `--search-mode Selected` before using `execute-dynamic-code`. Use when you need to: (1) Get details and component properties for selected GameObject(s), (2) Search for objects by name, regex, or path, (3) Find objects with specific components, tags, or layers. Use get-hierarchy when the child tree under the selection is needed. Returns hierarchy paths, active state, tags, layers, and components (or writes to a file when multiple GameObjects are selected).
37uloop-unity-search
Search Unity project assets using Unity Search engine. Use when you need to: (1) Find scenes, prefabs, scripts, materials, or other assets, (2) Filter assets by file extension or type, (3) Search with Unity Search query syntax and specific providers. Returns asset paths and metadata.
36uloop-clear-console
Clear all Unity Console log entries. Use when you need to: (1) Clear console before running tests or compilation, (2) Start a fresh debugging session, (3) Remove noisy logs to isolate specific output.
36uloop-run-tests
Execute Unity Test Runner and get detailed results. Use when you need to: (1) Run EditMode or PlayMode unit tests, (2) Verify code changes pass all tests, (3) Diagnose test failures with error messages and stack traces. Single-flight only — never run multiple `uloop run-tests` in parallel.
35uloop-launch
Launch Unity project with matching Editor version via uloop CLI. Use when you need to: (1) Open a Unity project with the correct Editor version, (2) Restart Unity to apply changes, (3) Switch build target when launching.
35uloop-get-logs
Retrieve current Unity Console entries via uloop CLI. Use when you need to: (1) inspect errors, warnings, or logs after compile, tests, PlayMode, or dynamic code execution, (2) search current Console messages or stack traces, (3) confirm whether a recent Unity operation emitted logs. Prefer this over reading Editor.log or Unity log files for normal Console contents; use log files only for startup, crash, freeze, or uloop connection failures.
35