MacroDroid vs Tasker: Which Android Automation App Fits Your Phone
MacroDroid, Tasker and Automate compared on free limits, permissions, Android version blocks, learning curve and download size, with three macros you can build now.

Most people install an automation app, build two macros, and forget it exists. That's fine. The app only has to fire when you're driving, asleep, or out of the house, and stay quiet the rest of the time.
The MacroDroid vs Tasker question comes up in every Android automation thread, and Automate usually gets mentioned third. All three solve the same problem in different ways, and the differences that matter aren't in the feature lists. They're in what the free build allows, which special permissions you have to grant before anything useful works, and how much of your evening the first real automation costs.
Catalog
- How the three compare at a glance
- The free versions, in plain numbers
- Permissions you'll be handing over
- Where Android versions get in the way
- Learning curve: an afternoon or a month
- Three macros worth building first
- Silence the phone at 23:00 on weeknights
- Warn me at 20% battery, but only when unplugged
- Open your music app when headphones go in
- Sizes, measured
- Who shouldn't install any of them
- Pick by how you think
- What you gain and what you give up
How the three compare at a glance
Sizes below are the APK files the store serves right now, not the installed footprint. More on that further down.
App | Download size | Price | Free build limit | Best for |
|---|---|---|---|---|
MacroDroid | 91.6 MB | Free with ads, Pro is a one-time purchase | 5 macros | A working macro in ten minutes |
Tasker | 31.3 MB | $4.49 on Google Play, 7-day trial | No free build | People who think in variables |
Automate | 10.0 MB | Free, Premium is one in-app purchase | 30 running blocks | Visual flowcharts |
The free versions, in plain numbers
The MacroDroid free version is ad-supported and caps you at 5 macros. That sounds generous until you build the obvious set: one for the car, one for work, one for sleep, one for charging, one for Wi-Fi at home. That's five, and the sixth idea waits. Pro removes the ads and the cap, and the developer sells it as a single purchase rather than a subscription, which is rare enough in 2026 to be worth saying twice. Triggers, actions and constraints are all available without paying, so you can test the app before you buy it.
MacroDroid is an Android automation app that streamlines everyday tasks on your device.
Automate limits running blocks instead of stored flows. Thirty blocks can be one flow with thirty steps, or fifteen two-step flows running at once. The developer's documentation is explicit that unconnected blocks inside a flow still count, so a half-finished diagram eats into the budget while it sits there. There's no cap on how many flows you keep on the phone.
Tasker has no free version at all. It costs $4.49 on Google Play, and the developer offers a 7-day trial as a direct download from his site. Seven days is enough to find out whether the profile-and-task model clicks. It won't be enough to finish the project you had in mind, which is either a sensible trial or a trap, depending on how you look at it.
Permissions you'll be handing over
None of these apps can do much with the permissions a normal app gets. The useful triggers live behind Android's special access screens, and each one is a separate trip into Settings.
Notification access lets the app read other apps' notifications, which is how "when my bank sends a payment alert" triggers work. Usage access tells it which app is in the foreground. Display over other apps allows floating panels. Alarms and reminders, required since Android 12, is what makes a 07:00 trigger fire at 07:00 instead of somewhere in the next hour. All files access, required since Android 11, lets file actions reach Downloads. Modify system settings covers brightness, screen timeout and rotation. DND access covers silent modes.
Then there's the one that decides whether an app can touch airplane mode, mobile data, dark theme or battery saver. Those settings sit in Android's protected tables and can only be changed with WRITE_SECURE_SETTINGS, a permission no app can request in the normal way. You grant it from a computer over ADB, or through Shizuku.
MacroDroid splits accessibility into two services so you enable only what a macro needs. The main service watches window and notification state and powers app-launched triggers, screen on/off, fingerprint gestures and screenshots. A second one, MacroDroid UI Interaction, performs taps and reads the screen hierarchy for macros that drive other apps. Its wiki lists every feature with the access it needs, which is more than most apps publish.
Tasker's version of the ADB step runs over Wi-Fi. You install the developer's Tasker Permissions app, run one command from a PC, and sometimes repeat it after a reboot. The developer's own guide warns that the command opens a port other apps can reach. That's an honest warning about a real tradeoff, not a reason to skip it.
Battery optimization is the other gate. Android will happily kill a background automation app, and several manufacturers go further. MacroDroid's troubleshooting page names Xiaomi, Huawei, Honor, Oppo, Vivo and Samsung, and sends you to dontkillmyapp.com for the vendor steps. On Xiaomi you need Autostart enabled or the app won't come back after a reboot. On Huawei and Honor the vendor task manager can close it even with a notification showing. Tasker's power management page points at the same site with less detail.
Where Android versions get in the way
MacroDroid requires Android 7.0 or newer. The other two don't state a floor as clearly on their listings, and older Android builds come with older restrictions anyway, so the version number isn't the interesting part.
What each release added is. Android 8 turned running automation into a foreground service, which is why these apps show a permanent notification. Hiding the notification is possible, and MacroDroid's own docs warn that the "force hide icon" option is known to get the app killed in the background. Android 11 locked down shared storage, so file actions now need All files access. Android 12 introduced the exact alarm permission, and without it a time trigger can drift by minutes. Android 13 made notifications a runtime permission, so a fresh install can end up with every warning muted until you allow them.
There's a quieter failure mode too. Accessibility services get switched off after some app updates, and force-stopping an app turns its accessibility and notification access off as a side effect. MacroDroid added a "Keep Accessibility Services Running" option for this, and restarting a killed service needs WRITE_SECURE_SETTINGS, so the fix depends on the ADB step you may have skipped.
Doze is the last one. A phone in deep sleep delays inexact alarms, which is why time triggers offer an exact-alarm option at a small battery cost. If your 23:00 macro fired at 23:40, that's the setting you missed.
Learning curve: an afternoon or a month
MacroDroid is the easiest to start with. You pick a trigger, add actions, add constraints, name it, save. The trigger list is searchable, so "battery" finds Battery Level in one tap. A template store holds user-made macros you can install and edit, and the system log records why a macro didn't run, down to the constraint that blocked it. Most people get a first macro working in ten minutes.
Automate asks you to draw. Flows are boxes connected by dots, executed top to bottom. That's clearer than a list when a task branches, and more annoying when it doesn't. The 30-block free limit means a complex flow has to be planned before you start dragging boxes. Expressions, variables and functions are there for people who want them, which is where the curve bends upward.
Tasker is the steep one, and its own users say so in reviews. The model is contexts for the "when" and tasks for the "what", with scenes for interfaces and variables for state. Once that clicks, Tasker does things the other two can't without plugins: conditional logic across dozens of states, JavaScript, intents, and a large plugin library. The price of that power is an interface that assumes you already know what a profile is.
An automation app for Android that can perform almost any task.
Three macros worth building first
These run in MacroDroid's free build without eating the whole 5-macro budget. The same ideas transfer to Tasker and Automate, with different names for the same three parts.
Silence the phone at 23:00 on weeknights
- Open MacroDroid, tap Add Macro, then Empty Macro.
- Tap Triggers, choose Day/Time, set 23:00, tap OK.
- Tap Constraints, choose Day of the Week, tick Monday through Friday.
- Tap Actions, choose Priority Mode, then set it to Alarms Only.
- Name it "Weeknight silence" and save. Grant DND access when asked.
You'll know it worked when the moon icon appears at 23:00. Build a second macro at 07:00 with the same action set back to All, or the phone stays quiet through Monday morning.
Warn me at 20% battery, but only when unplugged
- Add a macro and set the trigger to Battery Level, level 20, set to fire when it drops below.
- Add a constraint: Power Connected, set to false.
- Add the action Speak Text and type "Battery at 20 percent".
- Add Set Screen Timeout at 30 seconds if you want the warning readable.
The constraint is the part people forget. Without it the macro fires while charging, which is exactly when you don't care.
Open your music app when headphones go in
- Trigger: Headphones Insert/Remove, set to inserted.
- Action: Launch Application, then pick your music app.
- Optional constraint: Screen On/Off, set to screen on, so a pocket connection doesn't wake the phone and start playback.
This one needs no special access beyond app launching, which makes it a good test of whether triggers fire reliably before you build anything with location.
Sizes, measured
The APK the store serves for MacroDroid 6.1.5 is 91.6 MB. Tasker 6.6.18 is 31.3 MB. Automate 1.54.0 is 10.0 MB.
Don't read too much into the gap. A single APK can carry assets, translations and native libraries for several processor types, and installed size after optimization is usually smaller than the download. What matters more is that all three run a foreground service, so all three cost you a permanent notification and a little idle battery. Automate's 10 MB is the friendliest number here if storage is tight, not a sign that it does less.
Who shouldn't install any of them
If you won't grant accessibility or notification access, skip all three. You'd be left with time and charging triggers, which the built-in Modes and Routines on Samsung or the stock rules elsewhere already handle.
If the automation has to be reliable for something that matters, like medication or a security routine, a phone-based macro is the wrong tool. Doze, battery savers and vendor task killers all get a vote, and none of them ask you first.
If you want set-and-forget with no maintenance, know that every option here needs a check after each system update. Accessibility services get disabled, permissions get auto-revoked after months of background use, and notification access occasionally needs re-granting.
And if you're on iPhone, none of this applies. Shortcuts is the closest equivalent and it isn't the same product.
Pick by how you think
If you want | Install |
|---|---|
A working macro before your coffee goes cold | MacroDroid |
To see the logic as a diagram | Automate |
Variables, JavaScript and plugin chains | Tasker |
No subscription, ever | MacroDroid Pro or Automate Premium |
Zero cost across many automations | Automate's free build |
The largest library of ready-made macros | MacroDroid |
The split between MacroDroid and Tasker comes down to one question. Do you want to describe what should happen, or program it? MacroDroid takes the description and fills in the gaps. Tasker makes you define the gaps, then rewards you for it.
Automate sits between them and gets overlooked because flowcharts look like work. If you've ever sketched a process on paper, its model will feel familiar within an hour.
What you gain and what you give up
MacroDroid
- Template store means you rarely start from a blank macro
- System log names the constraint that blocked a run
- One-time Pro purchase, no subscription
- Largest download of the three
Tasker
- Deepest logic, with variables, JavaScript and intents
- Large plugin library and a long-running community
- Paid up front, with only a 7-day trial
- Interface assumes prior knowledge
Automate
- Flowchart model makes branching readable
- Smallest download and the most usable free tier
- 30-block cap forces planning on complex flows
- Smaller community than the other two
FAQs
- Does Tasker need root?
- No. Most profiles run with normal permissions plus notification and accessibility access. A few system-level actions need WRITE_SECURE_SETTINGS, which you grant over ADB or Shizuku without rooting.
- Can I move my macros from MacroDroid to Tasker?
- Not directly. MacroDroid exports its own format and Tasker uses XML project files, so the logic has to be rebuilt. The trigger and action names are close enough that a simple macro takes a few minutes.
- Will these apps survive Samsung or Xiaomi battery management?
- Only if you whitelist them. Exclude the app from battery optimization, then follow the vendor steps for your brand, which usually means enabling autostart and setting battery usage to unrestricted.
- Which one drains the battery least?
- It depends on the triggers, not the app. Time and charging triggers are close to free. Location, motion and screen-content triggers keep sensors or accessibility services awake and cost noticeably more.
None of the three will fix a phone that kills background apps, and all three will disappoint you if you build twenty macros in a weekend and never check them again. Start with one macro that saves you a daily annoyance. If it still fires after a week and a system update, you've found the app that matches your phone.