One recorder for everything your users touch.
Record the journey your users actually take: a web flow in Chrome, Chromium, Firefox or WebKit, a live Citrix, RDP, Azure Virtual Desktop, Omnissa Horizon or local Windows session, or an Android or iOS app on a mirrored device. Every step is captured with a validation and a screenshot, and every run is kept on a visual replay timeline you can watch back.
Coverage is not identical on every operating system. VDI and desktop recording needs Studio on Windows. On a Mac, Studio records web and mobile.
- Web
- Google Chrome, Chromium, Firefox and WebKit, the Safari engine.Records on Windows and on a Mac.
- VDI and desktop
- Citrix, Citrix Enhanced, RDP, Azure Virtual Desktop, Omnissa Horizon and local Windows applications.Needs Studio on Windows.
- Mobile
- Android emulators and phones, iOS simulators and iPhones.iOS needs a Mac, or a remote Mac.
Three ways in, one workload out.
The recorder is a part of LoadGen Studio 2026 rather than an application you buy on its own. Pick the kind of session you need to capture.
- Google Chrome
- Chromium
- Firefox
- WebKit (Safari engine)
Clicks, typing, keys, drags and iframes
Elements light up as you hover, so you see what will be captured.
A sync point on every interaction
Each step waits for its element and keeps a screenshot.
Readable locators
Edit them as role, text or test-id locators, or pick one from a screenshot.
| CLM-4821 | Travel | 42.50 |
| CLM-4820 | Software | 119.00 |
| CLM-4816 | Travel | 18.75 |
Locator
getByRole('button', { name: 'New claim' })Captured
1Navigate
/claims
2Validate on element found
+ screenshot
3Click "New claim"
getByRole(button)
Illustrative Studio screen with example content. Hover or focus an element in the page to highlight it, and switch the locator between role, text and test-id. Nothing here opens a browser or records a session.
- Citrix
- Citrix Enhanced
- RDP
- Azure Virtual Desktop
- Omnissa Horizon
- Local client
Record inside the live session
Drive the published app, and Studio captures every click and key.
Image, hash, pixel and control validations
Read the UI control tree on Citrix Enhanced, RDP, Azure Virtual Desktop, Omnissa Horizon and local apps.
Your default for a click
Mouse click, click control, or validate image or pixel colour first.
Windows only. On a Mac, Studio records web and mobile.
Step properties
- Target
- Submit · Button
- Action
- Click control
- Record as
- Delay after
- Think (randomised)
Validations
Image, hash and pixel.
Illustrative Studio screen with example content. Pick a session type, select a control in the published window, and change how a click is recorded. The UI control tree is read on Citrix Enhanced, RDP, Azure Virtual Desktop, Omnissa Horizon and local apps, so that option withdraws on the other target. Nothing here connects to a session.
- Android emulator
- Android phone
- iOS simulator
- iPhone
The device, mirrored in Studio
Click the picture to tap the phone. Right-click to validate an element.
Swipe and locator pickers
Build gestures and pick elements without code.
Guided setup
A toolchain check and an iPhone setup assistant.
Mobile recording uses a Mobile profile on your LoadGen Platform. Record iOS apps on a Mac, or connect Studio to a remote Mac.
Expenses
Claim card
CLM-4821 · Travel · 42.50
Captured
1Launch app
Expenses
2Tap
New claim
3Validate element
Claim card
Device
Pixel 8 · Android 15
Illustrative Studio screen with example content. Pick a target, then open the menu on the mirrored screen to choose between tapping, validating an element and picking a locator. Nothing here mirrors a real device.
Watch every run back. Fix the step that broke.
A time-lapse of every recording and replay
About five frames a second, stored next to the workload, not in it.
Expected next to current
On a failed step, the two frames sit side by side with synced filmstrips.
Fix with AI and run to here
The AI repairs that one step and replays up to it to prove the fix.
The full replay check is optional and is off by default. You choose when a take is replayed end to end.
“Run to here” and “Run from here” restart at any step, and “Fix with AI and run to here” sits beside them rather than replacing them. The AI is given the expected and the current frame for that one step. You keep the result or you do not.
Expected 00:41.2
Expenses · New claim
Category: Travel
Amount: 42.50
Receipt.pdf
Current00:41.2
Expenses · New claim
Category: Travel
Amount: 42.50
Receipt.pdf
New privacy notice for all users
AcceptVideo
Time
Actions
7. Click · getByRole(button, "Submit")
Illustrative Studio screen with example content. Select a step on the Actions band or scrub the timeline to compare the expected and current frames. The failure shown, a new consent banner covering Submit, is an example. The four step actions are not wired in this demo: nothing is repaired, replayed or sent to a model.
See the recorder on your own applications.
We record a journey you actually care about, in the environment you actually run, and show you the replay afterwards.
