Record the browser half with the extension and the desktop half with Record Desktop. Both land in the same step list, in the order you took them, and export as one file.
Demo Maker Pro records both halves of a workflow that crosses from a web browser into a Windows program, and keeps them in one demo. The Chrome or Edge extension captures browser steps as real HTML and CSS, streaming into the desktop editor as you click. Record Desktop captures a Windows window as images: one press of the capture key (F9 by default) per screen. 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, HTML export and publishing all behave identically whether the step underneath is markup or a picture. You save one .dmp project, export one self-contained HTML file, or publish one link.
Browser steps preserve HTML and CSS. Desktop steps use screenshots of the application window. Both support interactive guidance and can be combined in the same demo.
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 Windows 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, 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.
With the desktop app open and licensed, start the extension in your own Chrome or Edge, in your already-logged-in session. Steps stream into the editor as you click. 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, and the extension's Resize button sets it.
In the app, click Record Desktop, switch to the program, press F9 once per screen, then click Stop. The capture key is configurable, and while a session runs it belongs to Demo Maker Pro rather than the program underneath. "Capture one window only" pins capture to a chosen program instead of whatever is in front. Whatever was on screen is captured, including an open menu.
Browser and desktop steps appear together in the left sidebar in the order taken. Reorder by dragging or through the step's ⋯ menu; rename or delete from the same menu. 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.
This is what makes mixing worth doing rather than merely possible.
A workflow can start in a browser portal, continue in a Windows application, 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 Windows client and confirm that the new profile is applied."
If the whole workflow lives in a Windows application, skip the mix, see the Windows application demo recorder. 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 | $149/month (Publish) | Yes, Record Desktop, images | Yes, Export HTML |
| 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 requires a licensed copy of the Windows desktop application, open, while you capture, including for browser capture, because the extension streams into it. There is no macOS or Linux build, and the extension is Chrome and Edge only.
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, export the HTML file and host it behind your own access controls. When a paid plan ends you can no longer record, edit, export or publish, though exported files keep working. More in the documentation and interactive software training.
Yes. Record the browser part with the Chrome or Edge extension and the desktop part with Record Desktop. Both kinds of step land in one step list, in the order you took them, and export as one file.
No. Targets, tooltips, navigation, title pages, completion screens, HTML export and publishing work the same for both. The one difference is that text in a desktop step is part of the picture.
The Windows desktop application, open and licensed while you record. Browser steps also need the Demo Maker Pro extension in Chrome or Edge. Desktop Capture needs no extension.
A browser. Viewers need no account, license, extension or install, whether you send them an exported HTML file or a published link.
Try one workflow that crosses both windows. The trial is free for seven days.
Request trial