When the built-in tool is enough

A decade of app-installing habits was formed when operating systems did very little, and built-in tools did almost nothing. They now do a great deal, and much of what people still install has a version already on the machine.

The point is not to avoid apps. It is that an app should have to win, and most of the time nobody checks whether it needs to.

What is already there

Depending on your platform, these ship with the system and need no account:

• PDF — merging, splitting, rotating, signing, and basic annotation.
• Screenshots and screen recording, including window capture and region selection.
• Image editing — crop, rotate, adjust, convert between formats, remove backgrounds on newer systems.
• File compression, both directions, for common archive formats.
• Password management, synced across devices, with passkey support.
• Translation and dictation, increasingly on-device.
• Automation — Shortcuts on macOS and iOS, Power Automate on Windows — which covers a surprising amount of what people buy small utilities for.
• Text extraction from images, live in the photo viewer on both major mobile platforms.

Browsers add PDF viewing and annotation, a password manager, translation, reader mode, and profile separation.

Why built-in wins by default

No account. Nothing to sign up for, nothing to leak, nothing to be locked out of.

Updated with the system. A security fix arrives without you knowing it existed. An abandoned utility does not get one at all.

It cannot be acquired. The most common way a good tool becomes a bad one is a change of ownership, followed by a subscription, a new pricing tier, or a quiet shutdown. A system feature has none of those failure modes.

No cost, and no future cost. Free tools with no visible revenue eventually find one, usually at your expense.

The four questions that justify an app

1. Do you do this often enough for the difference to matter? A dedicated tool that is twice as fast at something you do twice a year has saved you nothing.
2. *Is it better at your specific task, or better in general?* Feature lists compare products; you are choosing for one job.
3. What does it need from you? An account, a subscription, file access, cloud upload. A built-in tool asks for none of these, so an app's asking is a real cost rather than a formality.
4. Can you get your work out? The same export question as always, and the one that decides whether choosing wrong is recoverable.

Where apps genuinely win

• Depth in one domain — a real photo editor, a real video editor, a real IDE. Built-in tools stop at the first 80%.
• Cross-platform consistency, if you move between systems and want the same behaviour on both.
• Collaboration, which the system's local tools mostly do not attempt.
• Batch and automation at scale, past what the built-in automation tools handle comfortably.
• A workflow you have already built, which has real value that a feature comparison does not capture.

Try the built-in one first, for a week, on the actual work. The comparison people usually make is between an app they used and a system tool they never opened.

A practical audit

Look at what you have installed and ask, for each: what does this do that the system does not?

You will usually find two or three that were solving a problem the platform solved since, and one you have been paying for annually without opening. Removing those is faster than any productivity system, and unlike a productivity system it stays done.

What are built-in tools?

Built-in tools are the features shipped with the operating system or browser — the PDF editor in the file viewer, the screenshot utility, the password manager, the automation app, the text extraction in the photo viewer. They are not accessories to the platform; they are the platform, updated with it and supported for as long as it is.

Their defining property is what they do not ask for: no account, no subscription, no upload, no publisher who can be acquired.

Where do built-in tools stop?

The pattern in the right-hand column: depth in one domain, scale, or collaboration. Everything else has been absorbed.

How long should you test before installing?

One week, on real work. The comparison most people make is between an app they have used for years and a built-in tool they have never opened, which is not a comparison at all.

Then 4 questions decide it: do you do this often enough for the difference to matter, is it better at your specific task rather than in general, what does it ask from you, and can you get your work back out. An app that answers all 4 well has earned its place. Most never get asked.

More on this in our comparisons, the alternatives worth knowing, and productivity software that justifies a subscription.

An audit worth half an hour

Open your applications list and ask of each one: what does this do that the built-in tools do not? Two or three will turn out to have been solving a problem the platform solved 3 years ago. One will be a subscription nobody has opened since renewal.

Removing those is faster than any productivity system, and unlike a productivity system it stays done. The Shortcuts user guide and the Power Automate documentation are the two references worth skimming first, because automation is the category where built-in tools have advanced furthest and where people are least aware of it.

The point is not that apps are unnecessary. It is that an app should have to win, and for most of what people install, nobody ever checked whether it needed to.

None of this argues against paying for software. It argues against paying for software that duplicates something already on the machine, which is a different and much more common mistake. The built-in tools have quietly absorbed a decade of small utilities, and the habit of checking has not caught up with them.

There is one more reason to check before installing, and it has nothing to do with cost. Every application is a publisher who can change, a permission you granted, and an update channel into your machine. The built-in tools carry none of those, which is worth something even when the feature comparison is a draw. The check is quick, it is free, and it is the one nobody performs before pressing install. Built-in tools are not a compromise; for most everyday work they are simply the answer nobody looked at. Try the one already on your machine before you go looking for another, and let the app prove it is needed.