RunMacroCompatibility0:55Coming soon
Windows compatibility overview
Review supported Windows versions and setup basics.
Help Center & FAQ
Frequently asked questions
Everything you need to know about RunMacro, pricing, setup, security, and automation modes.
Popular:
Can I use RunMacro for free?
Does it work on Windows 10/11?
Does Browser Mode take over my mouse?
Getting started
Installation, setup, first workflow and basics.
→Pricing & trial
Free trial, plans, payment, refunds and upgrades.
→Automation modes
Desktop, Browser and QMacro Runner.
→Security & permissions
Admin rights, data safety, cloud sync and privacy.
→Troubleshooting
Common issues, errors, logs and solutions.
→Account & support
License, devices, team, and how to contact us.
→RunMacro is a no-code automation tool for Windows. It lets you record or build a sequence of actions — clicks, keystrokes, waits, conditions — and replay them automatically so you don’t have to do repetitive work by hand.
It covers three kinds of automation: Desktop Mode drives the real mouse and keyboard on any Windows app; Browser Mode automates Chrome through the DevTools Protocol (CDP) without taking over your mouse; and QMacro Runner runs packaged workflows behind a simple input form. You can use one, two, or all three in a single project.
It is built for anyone who repeats the same computer task often: office staff doing data entry, marketers filling forms or managing many accounts, testers, virtual assistants, and small businesses.
You don’t need to be technical to start — beginners use recording, templates, and the visual element picker, while power users can add conditions, variables, HTTP requests, and even Python or C# when they need more control.
No coding is required to build useful workflows. You can record your actions and RunMacro turns them into editable commands, drag ready-made commands from the library, or start from a template.
Coding is entirely optional: advanced commands like Run Python, Run C#, HTTP Request, and Regex exist for people who want them, but you can build most real automations — data entry, form filling, web scraping, multi-account tasks — without touching any of them.
It is designed so beginners are not overwhelmed. The command library has a Basic tab with only the common, easy-to-understand commands, and an Advanced tab with everything, so you are not staring at seventy commands on day one.
When you open a new workflow you get big buttons for the three easiest ways to start — Record actions, Build with AI, or Use a template (plus Open an existing macro) — so you always have an easy starting point. The properties panel stays out of the way until you select a step, and errors are explained in plain language with buttons to fix them rather than raw technical logs.
No — they are two separate things. Basic vs Advanced is just a view of the command library that you can switch anytime; it controls how many commands are shown, not what you are allowed to use.
Free vs Pro vs Team is your license, which unlocks features. A Pro user can still work in the Basic view for a cleaner screen, and a Free user who switches to Advanced will still see paid-only commands (marked with a lock) rather than having them hidden.
Download the latest Windows installer from the Download page, open the setup file (usually in your Downloads folder), click Install, and wait for it to finish. Then open RunMacro from the Start menu or the desktop icon.
Because it is newly published software, Windows SmartScreen may show a warning. If it does, click "More info" then "Run anyway" to continue — and if you want to be sure the file is genuine, compare its SHA256 hash against the one on the Download page.
Yes. RunMacro is built for modern 64-bit Windows, specifically Windows 10 and Windows 11. Everything it needs to run comes bundled in the installer, so there is no separate runtime to set up — you just need an internet connection for updates and license validation.
Browser Mode additionally needs a recent version of Google Chrome installed, and the optional Run C# command needs a .NET/C# toolchain only if you use it. RunMacro is not currently available for macOS or Linux.
Pick by where your task lives:
- Desktop Mode — for Windows apps, games, or legacy software with no web interface. It uses the real mouse and keyboard, so it takes over the machine while running.
- Browser Mode — for anything in the browser (logins, forms, scraping, many accounts). It drives Chrome in the background over CDP and does not take over your mouse, so you can keep working.
- QMacro Runner — for running a finished, packaged workflow through a simple form, ideal for handing automation to non-technical people.
Many real projects combine Desktop and Browser mode in one workflow.
Open RunMacro, choose a mode (Desktop or Browser), and create a new macro. An empty workflow shows big buttons for the three quickest ways to start so you can pick the easiest path: Record your actions, describe the task and let AI build it, or start from a template.
From there, add or tweak a few commands — for example open an app or URL, type text, click a button — and always add a short wait after anything that loads. Press Run to test, watch it work, adjust, and save. Building in small steps and testing often is the fastest way to a reliable workflow.
Yes. There is a free tier you can use indefinitely, and the paid Pro and Team plans include a 14-day free trial. The trial does not require a credit card, so you can validate real workflows before paying anything.
During the trial you get the full paid feature set, which is the best way to confirm that Browser Mode, advanced commands, and cloud features fit your work. Exact limits are always listed on the Pricing page.
Free is for getting started: it covers Desktop Mode with basic mouse/keyboard actions and basic flow, on one device. Pro unlocks the full toolset — Browser Mode (Chrome/CDP), QMacro Runner, all advanced commands, conditions, image/color detection, the AI recorder, and cloud sync — also on one device.
Team is the same full feature set as Pro but licensed for up to 5 devices at a lower price per device, plus team template sharing. A detailed feature-by-feature comparison table is on the Pricing page.
The Free and Pro plans are licensed for one device each. The Team plan covers up to 5 devices under a single subscription, which is why its per-device cost is lower.
If you need to run on more machines than your plan allows, you can add seats or move to Team. To switch which machine a license is active on, deactivate the old device or ask support to reset it (see the support section).
Yes. Desktop Mode, Browser Mode, and QMacro Runner are all part of RunMacro and are unlocked by the same license according to your plan.
On Free you mainly use Desktop Mode; Pro and Team unlock Browser Mode and QMacro Runner as well. You never buy the modes separately — one paid license gives you all of them on your allotted devices.
Yes, you can change plans at any time and the change takes effect immediately. Upgrade when you need Browser Mode, more devices, or team features; you can also switch billing cycles (monthly, 6-month, or yearly) to save.
If you need help moving a license or adjusting seats, contact the RunMacro team and they will sort it out.
The payment methods currently available to you are exactly the ones shown at checkout and may vary by country or order. Enter a valid email before continuing.
After payment is confirmed, your license is shown in checkout and sent to that email.
Yes. All paid plans come with a 14-day money-back guarantee. If RunMacro is not the right fit within that window, contact support for a refund.
Because the paid trial is free and needs no card, the best approach is to trial the features first — that way you already know it works for your use case before you pay.
It depends on the current sales program and market. A one-time purchase option may be offered at times, but the standard plans are subscriptions (monthly, 6-month, or yearly) that include updates and support.
Check the Pricing page for the latest offers, or contact support to ask about one-time or business licensing.
1. Open https://runmacro.app/en/pricing. 2. Choose monthly, 6-month, or yearly billing. 3. Choose Pro or Team and continue to checkout. 4. Enter a valid email, choose a payment method currently displayed as available, acknowledge the Terms and Privacy Policy, then click Continue to payment. 5. Follow the instructions shown by checkout. After payment is confirmed, the license is displayed there and sent to your email. 6. To activate it, open RunMacro and go to Settings → License.
AI Unlimited is available for eligible active, fixed-term Pro licenses. In the RunMacro desktop app, open Settings → AI / API and choose Buy AI Unlimited. The server calculates a quote for the time remaining on your current Pro license and shows the amount before payment.
After payment is confirmed, the add-on activates for that license and expires with the current Pro license. While active, hosted RunMacro AI requests do not consume the normal daily or bonus credit quota. Service availability, request and attachment limits, acceptable-use rules, and abuse-prevention controls still apply. Reopen Settings → AI / API to verify that AI Unlimited is active.
It depends on the mode. Desktop Mode uses your real mouse and keyboard, so while it runs you should not touch the computer — the cursor is doing the work.
Browser Mode is different: it controls Chrome through the DevTools Protocol (CDP), sending clicks and keystrokes straight into the page. It does not move your physical cursor, so you can keep browsing, typing, or working in other apps while automation runs in the background. This is the main reason to choose Browser Mode for web tasks.
Explainer1:10Coming soon
Browser Mode vs Desktop Mode
See how Chrome/CDP automation runs without taking over your mouse.
Browser Mode connects to Chrome over the Chrome DevTools Protocol — the same interface developer tools use. Through it, RunMacro can navigate pages, click and type into elements by selector, read HTML and attributes, and extract data, all inside the browser engine rather than by moving the mouse on screen.
Because it works at the page level, it is more reliable than coordinate clicking (it survives layout changes) and it can run several Chrome windows or profiles at once. It is the right mode for logins, forms, scraping, and multi-account work.
Yes. Install the RunMacro Smart HTML Chrome extension to use Browser Mode and Smart Record. Desktop Mode and QMacro Runner do not require the extension.
Smart Recorder watches what you do and turns it into commands automatically — you don’t write selectors by hand. As you click and type, it detects the target elements for you and adds the matching steps to the workflow.
For web elements it also captures a fallback selector, so if the primary one changes the workflow can still find the element. Combined with the visual "Select" picker, this means most users never deal with raw CSS or XPath at all — you point, it captures.
Yes, absolutely. A selector is just the information RunMacro uses to find the right button or input on a page — and you never have to write one. Use the visual "Select" (picker) button: click the element on the page and RunMacro captures it, showing something friendly like "Selected: Email field" instead of a raw code string.
The full technical selector is tucked away under "Details" for advanced users who want it. For everyone else, pointing at the element is all you need.
Yes. Browser Mode automates Google Chrome specifically, through its DevTools Protocol, so you need a recent version of Chrome installed and configured as the browser source for RunMacro CDP.
Desktop Mode has no such requirement — it works with any Windows application. So if you don’t use Chrome, you can still automate desktop software; you just won’t use Browser Mode for it.
Yes. Browser Mode can drive several Chrome windows or profiles in parallel, which is how people run the same workflow across many accounts at once. Each profile keeps its own cookies and login, so sessions stay separate.
The practical limit is your machine’s resources: each Chrome window uses RAM and CPU, so keep the number reasonable for your hardware. Start with a few in parallel and scale up while watching performance.
You describe the task in plain language. AI then opens the page in background Chrome (CDP), observes the page structure (the DOM), and works out which elements to act on. RunMacro assembles that into a normal workflow of editable commands and shows it to you as a preview.
Nothing runs against your data until you accept it, and every generated step is a standard command you can review and edit. Treat the AI output as a fast first draft that you confirm — that combination is quicker than building alone and safer than a black box.
Yes — that is exactly what it is for. When an app exposes no web-style selector (legacy software, remote desktops, games, custom tools), Desktop Mode operates it visually: it clicks by coordinates, finds on-screen images with Find Image, matches colors with Find Multi-color, and can read text on screen with OCR.
So even a program that gives you nothing to hook into can still be automated, because RunMacro drives it the same way a person would — by looking at the screen and using the mouse and keyboard.
Yes. Switching the library to the Basic view only changes which commands appear when you add new ones — it never removes commands from existing macros. Any workflow you already built keeps all its steps and runs exactly as before.
Advanced commands inside older macros stay visible and functional; the Basic/Advanced toggle is purely about keeping the "add command" list simple for newcomers, not about disabling anything.
Your automation runs locally on your own machine. RunMacro executes the mouse, keyboard, and browser actions on your PC — it is not a cloud bot that runs your tasks on someone else’s server.
A few features do use the internet: license activation, update checks, optional cloud sync of your workflows, and AI features that call an external AI provider. Everything else — including reading the screen and driving Chrome — happens on the device in front of you.
RunMacro is safe when downloaded from the official website. New or lightly-downloaded Windows apps often trigger a SmartScreen or antivirus warning simply because they don’t yet have a long reputation history — it is not evidence of malware.
To be certain you have a genuine, untampered file, compare its SHA256 hash with the value published on the Download page. Always download from the official site and avoid re-uploaded copies from unknown sources.
Support1:20Coming soon
Admin permission explained
Learn when elevated permissions are needed and how to run safely.
No, not by default. The pages you automate and the data you handle stay on your machine; RunMacro only sends data for a feature you actively turn on.
The two exceptions are opt-in: cloud sync uploads the workflows you choose to sync, and AI features send the context needed for the request to the AI provider you configured. Your logins and page content are not transmitted for normal Desktop or Browser automation.
For everyday automation, no — normal user rights are enough to click, type, and drive Chrome. You only need to run as administrator in specific cases, such as automating another program that itself runs elevated, since Windows blocks a normal-privilege app from controlling an elevated one.
When a step genuinely needs elevation, RunMacro tells you; otherwise, run it as a standard app. Grant admin only when a task actually requires it.
Your workflows are saved as files on your PC (.pmacro for editable workflows, and packaged .qmacro files), so you own and control them like any other document. Settings and things like the AI key are kept in RunMacro’s local configuration on your machine.
If you enable cloud sync, a copy of the workflows you choose is stored in your cloud target so you can pull them onto another computer — but the local files remain the source of truth.
The AI API key is stored with a protection mechanism in RunMacro’s local settings on your own machine, and it is not shown again as plain text after you save it. It is used only to call the AI provider you configured.
Treat the key like a password: don’t paste it into shared workflows or screenshots. You can replace or remove it in settings at any time.
Yes. When you package a workflow as a .qmacro, you can protect it — for example with a password or encryption — depending on the export configuration, so recipients can run it without seeing or changing the underlying steps.
This is useful when handing automation to clients or teammates: they get a simple runner they can use, while your logic and any embedded details stay protected.
This is the most common web error and it almost always means the element wasn’t there yet or has moved. RunMacro shows a friendly error at the failing step with the likely causes and quick-fix buttons, so start there.
Work through the usual causes in order:
- The page hadn’t finished loading — add a Wait for element (or a short Delay) before the step.
- The site’s layout changed — use the "Select" picker to re-capture the element.
- The element is hidden or inside a popup/iframe — make sure the right tab or frame is active first.
Use "Run from selected row" to continue from that step after fixing, instead of re-running the whole workflow from the top.
When nothing on your side changed but a workflow suddenly breaks, the target usually changed. Websites and apps update their layout, rename elements, or log you out, and timing can differ on a slower day.
Diagnose it like this: open the logs to see which step failed and why, run the workflow step by step to watch where it diverges, then fix the specific cause — re-capture a moved selector, add a wait if a page is slower now, or re-authenticate if the session expired. Fixing one step and re-running from there is faster than rebuilding.
CDP connection problems usually come down to the Chrome instance or the port. Check that Chrome is launched the way RunMacro expects, with the correct debugging port, and that the profile you’re pointing at isn’t already open and locked by another Chrome window.
Also make sure no other program is using the same debugging port, close stray Chrome processes if a profile seems stuck, and confirm your Chrome version is recent. Restarting Chrome through RunMacro often clears a stale connection.
Two things cause this: racing the interface, and fragile targeting. If it acts before the screen is ready, add a Wait for element or a Delay after each step that loads something so RunMacro isn’t clicking too early.
If it clicks the wrong spot, prefer robust targeting: for web pages use the "Select" picker/Smart HTML instead of fixed coordinates, and for desktop apps use Find Image or Find Multi-color so it clicks what it sees rather than a pixel that shifted. Test on a small run and watch it once — most "wrong click" issues disappear once waits and reliable targets are in place.
Simulating individual keystrokes can clash with Vietnamese input methods (Telex/VNI) and drop or scramble characters. The fix is to paste instead of type: use Paste Text, which puts your content in and pastes it in one go, giving reliable results for Vietnamese and long strings.
As a rule of thumb, use Type Text only for short, plain ASCII where per-key typing matters, and use Paste Text for anything with Vietnamese characters, special symbols, or length.
Open the Logs panel in RunMacro to see a step-by-step record of a run, including which command failed and the message behind it. On a friendly error, the "Details" button reveals the technical information (selector, stack, data) when you need to dig deeper.
If you need help from support, use the log export feature to package the error information into a file you can send — it saves a lot of back-and-forth because the team can see exactly what happened.
This is a reputation warning for newer software, not proof of a virus. First confirm you downloaded from the official website, then verify the file’s SHA256 hash against the value on the Download page so you know it’s genuine.
Once verified, click "More info" then "Run anyway" on SmartScreen, or allow the file in your antivirus, to continue installing. Never bypass the warning for a file from an unknown or re-uploaded source.
If an archive of previous versions is available, you can get it from the Download page and install over your current version. Only roll back when you hit a genuine compatibility problem, since older builds miss the latest fixes and features.
Before downgrading, it’s worth checking the release notes and reporting the issue — a newer patch may already address it, which is safer than staying on an old build.
A license is tied to a device, so to move it you first free up the seat on the old machine — deactivate the license there if you still have access. Then activate on the new machine as usual.
If the old computer is broken, lost, or you can’t deactivate it, contact support to reset the device binding for your account. Team plans have several seats, so you may simply activate on the new machine if a seat is free.
Yes, in two ways. You can share the editable .pmacro file so another RunMacro user can open and modify it, or package the workflow as a .qmacro so someone can run it through a simple form without seeing or changing the steps.
The .qmacro option is ideal for non-technical colleagues or clients, and it can be password-protected. Team plans add shared template libraries so a whole team stays on the same version of a workflow.
RunMacro checks for updates and paid plans receive them automatically, so you normally just install when prompted. You can also check the current version and changelog on the Download page at any time.
Updates bring fixes, stability improvements, and new features, so staying current is recommended. If you rely on a critical workflow, test it briefly after a major update — and remember older versions are available for rollback only if a real compatibility issue appears.
Templates live in the in-app gallery, grouped as My Templates, complete Workflows, reusable Blocks, and Team templates. When you open a new workflow, "Use a template" is one of the three starting buttons, so you can begin from a ready-made automation instead of a blank canvas.
Each template carries a status badge — such as Ready to run, Needs configuration, Needs element selection, or Needs data — so you know at a glance what to adjust before running it for your own case.
Yes. Free users have the documentation, guides, and community channels, which cover the vast majority of questions. Paid plans (Pro and Team) add priority support — Pro gets email support and Team gets priority handling.
So everyone can get unstuck; paid plans simply get faster, more direct help when a problem is urgent or specific to your setup.
Start with the documentation and this FAQ, which answer most questions instantly. If you still need help, email support (the address is on the Download page) or use the community channels linked on the website.
When you report an issue, include your RunMacro version, the mode you were using, and an exported log if possible — that lets the team reproduce and fix it much faster than a description alone.
Still need help?
Can’t find the answer you need? Contact the RunMacro support team.
