When Demo Maker Pro captures real HTML and CSS, when it captures an image of a window instead, and why everything after the capture behaves identically either way.
Demo Maker Pro has two capture methods. Recording in Chrome or Edge captures real HTML and CSS. Desktop Capture records an image of a window. Which one you get depends only on how you recorded the step, and you can mix both in a single demo.
Browser recording captures real HTML and CSS, on every plan. That is the default and it is what keeps text selectable, fonts and spacing intact, and a single changed screen re-recordable on its own.
The extension records inside your own Chrome or Edge, in the session you are already logged into, and the steps stream into the desktop editor in real time as you click. See record a browser demo for the procedure.
Desktop Capture records an image of a window instead, because there is no markup to read out of a desktop program. Use it for applications that live outside the browser (a Windows application, a virtual machine window, a Java or Citrix client) or for the occasional web interface that will not snapshot cleanly.
Desktop Capture records the application window, not the whole screen, so there is nothing to crop afterwards. The honest trade: text in a desktop step is part of the picture rather than selectable page content, and whatever the window was showing is captured with it, including an open menu.
Browser steps and desktop steps land in the same step list, in the order you took them. One walkthrough can start in Chrome and continue into a Windows application.
Everything downstream is identical either way: targets, tooltips, navigation, title and completion screens, HTML export and publishing all work the same on both kinds of step.
Next: Edit your demo · All documentation