Record the browser part as real HTML and the desktop part as screenshot steps, with the same extension. Both land in the same step list, in the order you took them, and publish as one link.
Demo Maker Pro records both halves of a workflow that crosses from a web browser into a desktop program, and keeps them in one demo. The Demo Maker Pro extension for Chrome or Edge captures browser steps as real HTML and CSS as you click. For anything outside the browser, the same extension's Capture any app takes a screenshot step each time you press the capture shortcut (Ctrl+Shift+3 by default, Command+Shift+9 on a Mac) in the program you shared. Both kinds of step land in the same step list, in the order you took them.
From there, nothing is split. Targets, tooltips, navigation, the optional title page and completion screen, publishing and HTML downloads all behave identically whether the step underneath is markup or a picture. You get one demo and one link.
The workflows hardest to document hand off between a web console and something installed. Three shapes recur.
You change a policy, VLAN assignment or certificate profile in a vendor's web console, then switch to the desktop client to prove it took effect: the supplicant dialog, the adapter status, the client's log window. No DOM recorder reaches that second half.
The learner opens a ticket in a browser ITSM tool, then acts on it in a thick-client admin tool, an MMC snap-in, a Java console or a vendor management client. Splitting that into two demos breaks the point: it is one procedure.
Create the instance, security group and key in a cloud console, then open an RDP session or a terminal and finish on the machine itself. The remote session window captures like any other.
Open the extension in your own Chrome or Edge, in your already signed-in session, and click Start recording. Each click becomes a step. Pause a second or two between clicks so each captures fully, and record at the size you intend to present at: a 1536 x 864 window is a sensible default.
In the extension, under Capture any app, click Share a screen or window and pick the program. Switch to it and press Ctrl+Shift+3 (Command+Shift+9 on a Mac) once per screen; nothing is taken between presses. The shortcut works in every program and can be changed. Click Stop screen capture when you are done.
Click Finish and the editor opens at app.demomakerpro.com with browser and desktop steps together, in the order taken. Reorder, rename or delete them there. A desktop step arrives with its target box in the middle of the screen; drag it onto whatever you are pointing at.
You need not record the halves in order, or in one sitting: Add steps in the editor records more into the same demo.
This is what makes mixing worth doing rather than merely possible.
A workflow can start in a browser portal, continue in a desktop program, and return to the browser. Capture each part, arrange the steps in one editor, and use consistent guidance throughout.
Keep capture sizes similar across applications and add a short instruction when the task moves to another tool. For example: "Open the desktop client and confirm that the new profile is applied."
If the whole workflow lives in a desktop program, skip the mix: see desktop application demos. If it is entirely in a browser, see HTML interactive demo software.
Mixed capture is not unique and we will not pretend it is. Guideflow's own materials describe combining screen capture and HTML capture inside one guideflow, and desktop recorders are common, Navattic, Supademo, Guideflow, Storylane and Arcade all publish one. All of them, and us, capture the desktop as images or video rather than DOM.
Two things differ: what the HTML half costs, and whether you finish with a file you hold.
| Tool | Entry price for HTML capture | Native desktop capture | Self-contained HTML file you host |
|---|---|---|---|
| Demo Maker Pro | $99/month (Cloud) | Yes, Capture any app, images | Yes, on Pro ($149/month) |
| Supademo | $199/month, Business billed annually | Yes; HTML capture is for web-based applications only | Not documented, hosted Offline Demos Player |
| Guideflow | From $499/month, annual tier | Yes | Not documented |
| Arcade | Enterprise only, custom-priced | Yes | Not documented, offline is Enterprise |
| Walnut | Not described on Walnut's pricing page | Not documented | Not documented, offline is a paid add-on |
| Navattic | $500/month, Base billed annually | Yes, Windows and macOS desktop app | Not documented, PWA on Enterprise |
Figures are from each vendor's own published materials, checked October 2, 2026. Reprise and Tourial publish no prices, so none are quoted. "Not documented" means the vendor's materials do not describe it, not that it is impossible. Full working on the comparison page; the file-you-host argument on self-hosted interactive demo software.
Recording needs Google Chrome or Microsoft Edge with the Demo Maker Pro extension. Desktop steps are screenshots of what you shared, so a desktop program is captured on the computer it runs on, or through a remote session window.
Desktop steps give up what markup gives: text is not selectable or searchable, and a changed screen is recaptured as an image. If a workflow could be done entirely in a browser, capture it that way.
A published link is unguessable but not password protected, so treat it as public. If the demo shows an internal console, download the HTML file on Pro or Team and host it behind your own access controls. More in the documentation and interactive software training.
Yes. Record the browser part with the Demo Maker Pro extension in Chrome or Edge, and the desktop part with Capture any app in the same extension. Both kinds of step land in one step list, in the order you took them, and publish as one link.
No. Targets, tooltips, navigation, title pages, completion screens, publishing and HTML downloads work the same for both. The one difference is that text in a desktop step is part of the picture.
Google Chrome or Microsoft Edge with the Demo Maker Pro extension. The same extension records web pages and, once you share a screen or window, desktop programs. The editor runs in the browser, so there is nothing else to install.
A browser. Viewers need no account, extension or install, whether you send them a published link or, on Pro and Team, a downloaded HTML file.
Try one workflow that crosses both windows. The trial is free for seven days.
Try it for free