How to Take Screenshots or Record Your Screen in VMware: A Complete Guide

If you work daily with desktops and virtual machines , knowing how to capture or record your screen in VMware saves you time and helps you document issues, evidence, and tasks. This guide covers the most useful methods for Horizon, Fusion, and vSphere environments, as well as alternatives for Linux and cloud scenarios.

Throughout this text, you'll find tips , shortcuts, and built-in options, as well as how to automate VM snapshots and what precautions to take regarding privacy and security . We've covered everything: from the basic Print Screen key to advanced utilities, including VMware client options and automated workflows.

Screenshot vs. VM Snapshot: Different Concepts That Shouldn't Be Confused

Before we get down to business, it's worth differentiating between two terms that are sometimes confused: a screenshot is an image of what you see on your virtual desktop or VM; a VM snapshot is a restore point of the virtual machine, with its disk state and, if you choose, its memory.

In vSphere environments and automation runbooks, there is a specific activity called " Take VM Snapshot ." This action creates a snapshot of a running virtual machine and allows you to name and describe it. It's useful for cloning, testing changes, or reverting if something goes wrong, but it doesn't generate a PNG/JPG image of the screen.

What properties do you need to define when creating a snapshot using a flow? There are usually three required ones: Snapshot Name (string), VM Memory Capture (boolean to include RAM state), and VM Path (identifier or path to the VM object). You can also add an optional description to help you remember its purpose.

These runbook activities publish data upon completion: the snapshot name and description , whether memory was included, and the path to the source VM. This allows other workflow steps to be automatically chained together, for example, to tag resources or create a new VM based on the existing configuration.

The typical setup in the runbook designer is simple: drag the "Take VM Snapshot" activity, open it, and in the Properties tab, select the VMware vSphere server connection (using the ellipsis button…), fill in the required fields, and if a property supports search, use the adjacent (…) button to locate values. You can also inject published data from previous activities and finish with a click on Finish.

How to take screenshots in VMware Horizon Client

VMware Horizon Client is designed to deliver a seamless virtual desktop and application experience, and taking screenshots within the client is as easy as on a local PC. In fact, you can combine native system shortcuts with tools built into the Horizon client itself.

Common keyboard shortcuts in Windows : the Print Screen key (PRTSC) copies the entire screen to the clipboard ; Alt + PRTSC copy the active window; and Windows + Shift + S opens the Snipping Tool (Snip & Sketch) to select an area. If you prefer to save directly, Windows + PRTSC automatically creates the file in the "Screenshots" folder within Pictures.

The Snipping Tool gives you complete control: open it from the search bar, click "New," choose freeform, rectangular, window, or full screen, select the area, and save the result from "File > Save As." It's very handy when you only want to capture a specific part of your virtual desktop.

Horizon also includes its own built-in option. From the client toolbar, open the " Options " menu and select "Take Screenshot." The screen will freeze briefly, and you'll see a dialog box where you can choose the location and filename before saving . It's a straightforward and hassle-free way to capture a screenshot from within the remote session.

Where are screenshots saved? By default, many Horizon settings point to the device's desktop , but you can change this. In the "File > Preferences > General" menu, you'll find "Screenshot Save Location": tap "Browse" to define a different folder and confirm with OK to save it.

If you work with multiple monitors, Horizon lets you capture several screens at once, either to separate files or to your clipboard, depending on your system settings. You can then organize them into folders, rename them with descriptive titles, and include them in reports or tickets.

VMware Fusion Pro on macOS: Keyboard, Mouse, and Capture Keys

On a Mac , with VMware Fusion Pro and VMware Tools installed, normally when you click inside the VM, all keyboard and mouse input is directed to the virtual machine; if you click on the macOS desktop, the focus returns to the host. This input capture can be forced so that everything stays in the VM when needed.

To take screenshots in Windows sessions within Fusion, you can use either macOS or Windows keyboard shortcuts. If you prefer to capture from the host, macOS offers Command + Shift + 3 (full screen) or Command + Shift + 4 (selected area). If you're capturing from within the VM, the classic shortcuts (PRTSCN, Alt + PRTSCN, etc.) will work just as well, as long as the keyboard focus is on the virtual machine window.

In scenarios where the "Print Screen" key doesn't physically exist on your keyboard, Fusion can map it, or you can use alternative system shortcuts. In either case, keep in mind that your keyboard layout and how the VM captures focus influence which shortcut is actually used.

Linux, Print Screen keys, and VMware menu options

On some Linux desktops, the "Print Screen" key is mapped differently, and depending on the keyboard layout, its equivalent might be codes like F13 or F14 . If you're unsure of the assignment, you can check it in the graphical environment settings or the shortcut preferences of the guest operating system .

Another valid option is to capture from Linux itself with its capture tool (for example, the one from GNOME or KDE) and then copy the image out of the VM using shared clipboard, shared folders or drag and drop if you have it enabled in the client.

Additionally, keep in mind that VMware usually has a "capture screen" option in its menu. This is especially useful when you're unsure about key mapping or when the guest and host keyboard layouts don't perfectly match.

Screen Recording: Native and Simple Alternatives

For video (not just still images), you can use native tools in the guest operating system. On Windows, the Game Bar (Win + G) lets you record the current window; on macOS, "Command + Shift + 5" opens the Capture panel with a recording option; on Linux, desktops like GNOME offer integrated recording, and there are utilities like SimpleScreenRecorder or OBS Studio.

Recording from the guest system usually yields better results than recording from the host because you capture exactly what happens within the session. However, be sure to monitor the VM's CPU and disk usage and save the videos in a folder that you can easily sync with the host to speed up the transfer.

Automating snapshots in vSphere with runbooks (not to be confused with snapshots)

Returning to VM snapshots, in orchestration environments you can insert the Take VM Snapshot activity into a runbook to create restore points before critical changes. This activity publishes output data with all relevant information (name, description, VM path, and whether memory was included) so the workflow can continue with subsequent steps.

The typical process is: drag the activity to the diagram, double-click it, use the ellipsis button (...) to choose the vSphere server connection, complete the snapshot name, check or uncheck "include memory," specify the VM path, and add a description if desired. Then, you can chain cloning actions or notifications based on the published data.

Keep in mind that including memory increases the size and time of the snapshot, but it allows you to revert to the exact state of execution. If you only want a point to revert the disk , uncheck that option to speed up the process and reduce the impact.

Cloud Captures: Screenshot Tool in Google Compute Engine

If you manage VMs in the cloud, platforms like Google Compute Engine offer a console capture tool that helps diagnose inaccessible instances (for example, whether they are booting or if there is disk corruption). It's a different approach than on-premises VMware, but useful for those who combine both environments.

Requirements and limitations: The instance must be in the RUNNING state , only one image can be captured at a time, and the maximum rate is 20 per second (API limit). Additionally, you need permissions such as compute.instances.getScreenshot to execute the action.

Before starting, it's advisable to enable the virtual screen on the VM and have authentication configured if you're using gcloud or the API. In the web console, simply go to "VM Instances > Instance Details > Screenshot Tab" and click "Refresh" to generate the screenshot.

If you prefer the command line , the command is straightforward:

gcloud compute instances get-screenshot VM_NAME \
  --destination=JPEG_FILENAME \
  --zone=ZONE

Replace VM_NAME with the instance name, ZONE with your zone, and if you don't specify JPEG_FILENAME, send the output to stdout.

With the REST API, the call is:

GET https://compute.googleapis.com/compute/v1/projects/PROJECT/zones/ZONE/instances/VM_NAME/screenshot

You must replace PROJECT, ZONE and VM_NAME with the values ​​of the project and the instance to be captured, keeping in mind the necessary permissions.

Privacy in remote desktop clients: Because capture uses the video adapter to capture the local console session, you could expose sensitive user desktop data. To prevent this, configure your remote client not to use the local console: in Chrome Remote Desktop, enable Curtain Mode; in Microsoft RDP , configure Remote Desktop Services to create new sessions instead of docking to the console.

Examples of use in Windows: a screenshot might show the UEFI loading the boot manager , a Windows Server 2016 applying updates, the system service starting, the login screen, the Sysprep process in Windows Server 2019 Core, or even a blue screen . These images greatly speed up the diagnosis when RDP fails.

Good security and privacy practices when capturing

Whenever you take a screenshot or record video, check for any sensitive data (credentials, browser tabs, emails). Be sure to hide or mask this data before sharing it with support or third parties, and review your company's policies regarding evidence handling.

Avoid capturing the local console when using remote desktops unless absolutely necessary, and if it is, add a layer of protection (such as Curtain Mode). Keep your clients (Horizon, RDP, CRD) up to date and restrict permissions so that only authorized personnel can generate and download screenshots.

Third-party software and organizing your captures

If you need more advanced features (scrolling windows, timers, annotations), try tools like Snagit, Greenshot, or Lightshot . They offer editing options and saving workflows that might be a better fit if you frequently create documentation.

To stay organized, create a dedicated folder for each project or client and use descriptive file names (date, VM, symptom). This will help you quickly locate evidence when preparing a report, opening a ticket, or sharing with a colleague directly from the VMware client interface.

Between system shortcuts, the Horizon toolbar, the VMware menu option to "capture the screen," host utilities (macOS or Linux), and third-party tools, you have a range of solutions to cover all kinds of scenarios. And if you need to "go back in time" on a VM, remember that a snapshot is the correct mechanism, different from a screenshot.