You have the program open. Here is the whole procedure, start a desktop recording, press one key per screen, place the targets, write the tooltips, export or publish.
Demo Maker Pro's Windows application does this on its own. Desktop Capture needs no browser extension.
Open Demo Maker Pro and click Record Desktop. Before you switch away, set the capture key if you need to (F9 is the default) and decide whether to turn on Capture one window only. Then switch to the program you want to record.
Work through the task exactly as you would demonstrate it. Every time the screen shows something the viewer needs to see, press the capture key. Nothing is being filmed in between, so you can pause, read, and think. When the workflow is finished, return to Demo Maker Pro and click Stop.
Each captured screen is now a step in the left sidebar. Drag its target box onto the control you were pointing at, write the tooltip, reorder anything out of sequence, then either Publish > Export HTML for a single self-contained file or Publish > Publish to DemoMakerPro for a shareable link.
F9 is the default and it is configurable, which matters more than it sounds. While a desktop capture session is running, the capture key belongs to Demo Maker Pro and does not reach the other program. If the application you are recording already uses F9 for something (and plenty of engineering tools, IDEs, terminal emulators and line-of-business applications do) you will press it expecting the application's behaviour and get a screenshot instead.
So before you start, check what the target program does with F9. If it is in use, change the capture key to something the application ignores. Pick a key you will not press by reflex during the workflow, or you will finish with a step list full of screens you did not mean to take.
The reverse case is also useful: if part of your walkthrough is about a function key, move the capture key out of the way so you can still demonstrate it.
By default the capture takes whatever is in front. Turn on Capture one window only and it pins to the program you choose. Now you can keep your script, a ticket or the procedure document on a second monitor, glance at it between screens, and none of it appears in the demo. This is the setting to use whenever you are recording from notes.
Whatever is on screen is captured, including an open menu. So to show a dropdown, a context menu or a ribbon flyout, open it and then press the capture key, the menu is in the picture. This is where a rebound capture key earns its keep, because you need a key that will not dismiss the menu you just opened.
Browser capture works through the Chrome or Edge extension, in your own browser. An embedded web view inside a native application is not Chrome or Edge, so the extension cannot see it, capture those screens with Desktop Capture like the rest of the window. If the same screen is also reachable in a real browser, capture that part separately in Chrome and you get real HTML for it.
Browser steps and desktop steps land in the same step list in the order you took them, so a walkthrough can start in Chrome, move into the Windows application, and come back again. The mixed recorder page covers that combination.
Fewer than a video would show, and more than a set of slides. The working rule: capture one screen for every point at which the viewer has to make a decision or find a control. A dialog opening is a screen. Typing three fields in that dialog is one screen, not three, unless one of the fields is the hard part.
When in doubt, over-capture. Deleting a step afterwards takes two clicks from the step's ⋯ menu, whereas a missing screen means going back into the application and recording again. The same menu renames steps, and steps can be reordered by dragging, so the order you press the key in does not have to be final.
Two things bracket the sequence if you want them: an optional title page before the first step and a completion screen after the last. Between them, remember that a step does not have to have a target. Turn the target off and the step advances by the tooltip's Back and Next buttons. That is how you add an explanatory screen without pretending there is something to click. The Target tab warns you if a step would end up with no way forward.
The same workflow, captured two ways.
⋯ menu.A desktop step is an image of a window. The text inside it is part of the picture and is not selectable, searchable or readable by a screen reader. That is the honest trade for reaching software that has no markup to read, a Windows application has no DOM, so nothing can capture one. If the workflow you are recording happens to live in Chrome or Edge, record it with the browser extension instead and you keep live text; see desktop interactive demo software for where that line falls and how other vendors handle it.
Two smaller practicalities. Capture at the size you intend to present at, Demo Maker Pro scales a demo down to fit a smaller screen but never enlarges it beyond the recorded size, so 1440 or 1920 wide is a good default. And an exported HTML file opened by double-clicking it in Explorer can look soft; serve it over http instead. Published demos are not affected.
Publish > Export HTML writes a single self-contained file with everything the demo needs inside it. Put it on your own intranet, embed it in an LMS, or email it. It keeps working regardless of your subscription and does not contact our servers.
Publish > Publish to DemoMakerPro uploads it and returns a link on demos.demomakerpro.com. Publishing the same project again updates that demo in place, so a link already sent stays current. Manage or remove them from File > My Demos; deleting takes the link down immediately. A published link is unguessable but not password protected, so treat it as public.
Either way, viewers need no account, no licence, no extension and no install, the demo opens in any browser. Keep the editable project with File > Save Demo (.dmp); large projects take a while to write and the app shows progress and a timer. Full detail on every setting is in the documentation, finished walkthroughs are on examples, and plans start at $59/month on Creator. If you are building this for a class or an onboarding programme, interactive software training is the relevant page.
Seven days free. A card is taken at signup and charged nothing that day. Install, press Record Desktop, and have a clickable Windows walkthrough before the end of the day.
Start your free 7-day trial