The post What Is System Data on Mac and Why Is It 100GB? (Real Fix, Not Guesswork) first appeared on Pinturas Ribo.
]]>Disclosure: this article links to CleanMyMac, a commercial product developed by MacPaw. We may earn a commission from purchases made through those links. CleanMyMac is Apple-notarized and distributed through the MacPaw Store, Setapp, and the Mac App Store. Every method described here also works manually at no cost, and the manual method is shown first in every case.
Key takeaways:
System Data is a reporting category in the macOS storage breakdown, not a directory you can navigate to. When macOS builds that breakdown, it sorts what it can into named buckets — Applications, Documents, Photos, Mail, Music, Messages — and everything it cannot confidently classify falls into the remainder. That remainder is System Data.
This matters more than it first appears. The category is defined by exclusion, which means its contents are heterogeneous by design. Caches sit next to swap files, which sit next to disk images, which sit next to fonts and plugins and log files. Nothing about being counted as System Data implies a file is systemic, protected, or important.
The practical consequence: the size of System Data carries almost no diagnostic information on its own. Two machines showing an identical 100 GB can be in completely different situations — one holding months of local snapshots, the other holding a single oversized virtualization image. Any advice that tells you to reduce System Data without first establishing what is inside yours is guesswork.
The category is a catch-all, but in practice a limited set of things account for most of its volume.
| Contents | Typical location | Shrinks on its own? | Safe to reduce? |
|---|---|---|---|
| Local Time Machine snapshots | Managed by tmutil; not visible in Finder |
Yes, eventually | Yes, at the cost of restore points |
| User and app caches | ~/Library/Caches |
No | Yes — apps rebuild them |
| Virtual memory swap | Managed by the system | Yes, on restart | No — leave it alone |
| Application support files | ~/Library/Application Support |
No | Only for apps you have removed |
| Log files | ~/Library/Logs, system log stores |
Partially, via rotation | User logs yes; system logs leave alone |
| Disk images and VM containers | App-specific | No | Only through the owning app |
| Developer build artifacts | ~/Library/Developer/Xcode/DerivedData |
No | Yes — regenerates on next build |
| Old iOS device backups | ~/Library/Application Support/MobileSync/Backup/ |
No | Yes, if the device is gone |
| Spotlight index | Hidden index stores per volume | No | Only via a supported rebuild |
| Fonts and plugins | ~/Library/Fonts, various plugin folders |
No | Rarely worth touching |
Two rows deserve emphasis because they cause the most confusion. Swap appears in System Data and looks like waste, but it is the system doing its job under memory pressure; deleting it is neither possible nor desirable, and it clears on restart. Disk images almost never shrink when you delete their contents — freeing space inside a virtual disk leaves the image file on your real volume exactly as large as before, and reclamation has to be triggered through the application that owns it.
A System Data figure in the hundred-gigabyte range is rarely the result of slow accumulation across many categories. In most cases one or two sources dominate, and identifying which is the entire job.
When a Time Machine destination has not been seen for a long time, macOS keeps local snapshots on the internal volume rather than discarding them. On a machine whose backup drive lives in a drawer, these can accumulate over weeks. This is the single most common cause of a large, mysterious System Data figure.
Disk images used by virtual machines and container tooling grow as they are written to and do not shrink when data inside them is deleted. A developer who has been building and discarding container images for months may be carrying a very large file that appears nowhere obvious in Finder.
Build output directories accumulate across projects and branches. They regenerate on the next build, which makes them safe to clear, but nothing removes them automatically.
Backups made through Finder persist indefinitely, including backups of devices you no longer own. Each one can be substantial, and there is no prompt suggesting you review them.
Uncommon, but it happens, and when it does the effect can be dramatic. An index that has failed in a loop can consume space far beyond anything reasonable for the volume it describes. This is worth suspecting only after the more common causes have been ruled out.
Before reducing anything, establish which of the above applies. These commands read only.
Start with real free space, unmediated by the storage breakdown’s arithmetic:
df -h /System/Volumes/DataThen check whether snapshots are involved:
tmutil listlocalsnapshots /
tmutil listlocalsnapshotdates /A long list with dates stretching back weeks confirms the most common cause outright. An empty list rules it out and moves you down the list.
Then find the large directories:
du -sh ~/Library/* 2>/dev/null | sort -rh | head -20sudo and traverses the entire data volume, which can take several minutes. It reads only and deletes nothing, but back up before acting on what it shows.
sudo du -xh -d 2 /System/Volumes/Data 2>/dev/null | sort -rh | head -30Run it twice a few minutes apart and compare. A directory that changes size between runs is being actively written to, which is a different problem from one that is merely large.
If working through directory listings is not how you want to spend an afternoon, a Mac storage optimizer will map the same territory visually in one scan. The commands above cost nothing and tell you the same thing, so run them at least once — knowing where your space goes is worth more than any single cleanup.
Order matters. Work from lowest risk upward and stop when the number is reasonable.
~/Library/Caches subfolder by subfolder rather than emptying it wholesale, so you can confirm nothing breaks as you go.The step-by-step procedure for each of these, with the exact paths and the order that reclaims the most space fastest, is covered in the companion cleanup guide rather than repeated at length here.
App leftovers deserve a note of their own, because they are counted in System Data and are invisible in Finder. Removing an application leaves its support files, preferences, caches, and logs behind in four separate locations, and the residue accumulates for years across apps you no longer remember installing. Hunting four folders per application manually is tedious rather than hard, which is where CleanMyMac app genuinely saves time: an uninstaller module catches all four in one pass. It is developed by MacPaw and Apple-notarized, which is worth verifying in a category that has historically attracted scareware.
You cleaned up, and System Data is unchanged. Three explanations cover nearly every instance.
The pane has not caught up. The storage breakdown recalculates on a delay, and Spotlight often needs to reindex changed folders first. Give it a full hour before concluding anything. Judging a cleanup thirty seconds after finishing it is the most common self-inflicted confusion in this entire topic.
A snapshot still holds the blocks. If a local snapshot predates your deletion, it references those file blocks so the backup remains restorable. The space returns when the snapshot ages out or is removed, not when you press delete.
It regenerated. Sync clients re-download libraries. Logs fill again. Build systems rebuild. If the figure returns within minutes rather than days, something is actively writing, and the repeated du comparison above identifies it.
Listed last deliberately — reconnecting the backup drive is better whenever it is possible.
tmutil listlocalsnapshotdates /
sudo tmutil deletelocalsnapshots [date-from-the-output-above]sudo and permanently removes a restore point. Only delete snapshots whose dates you have confirmed in the listing output, and never remove your most recent snapshot unless a current backup exists elsewhere.
Reducing System Data addresses caches, snapshots, backups, artifacts, and leftovers. It does not shrink your Photos library, your Documents, or applications you actively use — none of which are counted in System Data anyway. If the figure stays high after everything above, the remaining candidates are narrow: a corrupted Spotlight index needing a rebuild, a log in a failure loop, a snapshot that will not release, or a disk image whose owning application must reclaim it.
It also will not help if the volume is simply too small for the workload. A machine that fills again every few weeks despite a clean System Data figure is telling you something about its capacity, not its hygiene, and the answer is external or cloud storage rather than another cleanup.
Whether you use CleanMyMac app for system cleaning or its malware scanner, both make maintaining your Mac effortless. If you haven’t tried CleanMyMac yet, it’s one of the most effective tools for macOS.
It is a leftover reporting category, not a folder. macOS sorts storage into named categories and puts everything it cannot classify into this one. In practice that means caches, logs, local snapshots, swap, application support files, disk images, plugins, and fonts sitting together. Because the category is defined by exclusion rather than by content, its size alone tells you very little, and two Macs showing the same figure can have entirely different underlying causes.
Figures that large usually trace to one or two dominant sources rather than gradual accumulation. The most common are local Time Machine snapshots on a machine whose backup drive is rarely connected, virtualization or container disk images that grow without shrinking, developer build artifacts, and old iOS device backups. A corrupted Spotlight index can also inflate it dramatically. The number itself does not identify which applies, which is why diagnosis matters more than cleanup here.
You cannot delete it directly, because it is a category rather than a location. You reduce specific things counted within it, and safety varies enormously. User caches and build artifacts are safe and regenerate automatically. Snapshots can go but cost restore points. Swap and anything on the protected system volume should be left alone entirely — System Integrity Protection blocks the latter regardless. Never delete files simply because they are counted as System Data.
Usually the pane has not recalculated yet — it lags by up to an hour and often waits for Spotlight to reindex. Failing that, a local snapshot predating your deletion may still hold the blocks, so the space cannot be released. The third possibility is that the data regenerated immediately, which is common with sync clients and virtualization images. Wait a full hour before assuming the deletion failed.
Apple publishes no official figure, and any specific number quoted elsewhere is an observation rather than a standard. The trend on your own machine is more informative than the absolute value. A figure that stays roughly stable month to month is behaving normally whatever its size. One climbing steadily without a corresponding change in how you use the Mac indicates accumulation worth investigating, even if the current number looks unremarkable.
Locally cached iCloud content is generally attributed to its own categories, such as Documents or Photos, rather than to System Data. The sync machinery around it does contribute, though — cache directories, transfer staging areas, and partially downloaded files all land in the catch-all. A sharp rise right after enabling a large iCloud library points at the sync process, and the figure usually settles once initial synchronization finishes.
The post What Is System Data on Mac and Why Is It 100GB? (Real Fix, Not Guesswork) first appeared on Pinturas Ribo.
]]>The post Calculator Notepad Apps: The Full Guide (2026) first appeared on Pinturas Ribo.
]]>A calculator notepad is a plain-text editor that solves each line as you type it, showing the answer beside the line and keeping every line editable afterward. You get a calculator’s speed with a document’s memory, so changing a number near the top updates the totals below it. Numi, Soulver, and Calca are the apps that built the category on macOS, and Apple’s Math Notes is a limited version of the same idea shipped with the OS.
Key takeaways
Plenty of apps compute things. Not many are calculator notepads. Four traits separate the category from everything adjacent to it.
First, evaluation is inline and continuous. There’s no equals key. You type 18 * 4.5 and the answer appears at the right edge of that line before you’ve finished thinking about the next one. Second, the input stays as text. It doesn’t get consumed into a display register. You can click back into any line, change one digit, and everything downstream recalculates. Third, lines can reference each other, usually through named variables or a keyword like sum or prev. Fourth, the parser accepts more than arithmetic symbols. Units, currency codes, percentages, and date words all resolve inside the same line.
Drop any one of those and you have something else. An app with inline evaluation but no line references is a fancy Spotlight. An app with references but no natural-language parsing is a spreadsheet with one column. The combination is what makes the format feel different from both of its neighbors.
Here’s a document I actually keep around, reproduced exactly:
rate = 85
hours = 6.5
revisions = 3
hours * rate
revisions * 40
sum - 200Three inputs at the top, three lines of math below. Next month I change hours to whatever it was, and the three answers below update without me touching them. That’s the whole pitch. A pocket calculator can’t hold it. A spreadsheet can, but building the equivalent means creating a file, naming cells, and writing formulas that reference them, which is roughly two minutes of setup against about fifteen seconds of typing.
The subtle part is the third line. sum adds the results of the lines above it, so subtracting a deposit is one token rather than a reference chain. Different apps spell this differently, and the exact keyword behavior is the most common source of confusion when someone moves between them.
Soulver arrived with a specific complaint at its center: spreadsheets were overkill for the math people did most often, and pocket calculators were too limited to hold more than one number. Its answer was a notepad with a results column. Type a line, see an answer beside it, keep typing.
The interaction that mattered most turned out to be seeing the result appear during typing rather than after a keypress. That collapsed the gap between writing a problem and solving it, and it’s the thing every later app in the category copied without modification. Soulver also introduced line references, letting a later line point at an earlier one, which is what turned the format from a nicer calculator into something you’d save.
Calca went academic. Built around Markdown documents and symbolic algebra, it let a user write x + 15 = 40 and solve for x rather than only evaluating expressions with known values. That’s a genuinely different capability, closer to a lightweight computer algebra system, and it earned a smaller but devoted following among people working through algebra inside a text file.
Calca’s development pace slowed considerably after its early releases. The symbolic solving still works and still has no direct equivalent in the other apps, but anyone choosing it in 2026 should weigh that capability against the update cadence.
Numi took the same core format and optimized a different axis. Instead of a document editor you open and keep open, it’s a window you summon with a global hotkey, type one line into, and dismiss. Documents exist and save fine, but the design assumption is that most calculations are disposable and the cost of reaching the app matters more than the cost of organizing results.
That distinction explains why three apps built on one idea never collapsed into one product. They’re optimizing different halves of the same workflow. The parsing details behind Numi mac follow from that same speed-first assumption: a local grammar rather than a network call, because a round trip would defeat the point.
Apple adding Math Notes to the Calculator app is the most consequential recent event in the category. A version of the format now ships with macOS, handles basic arithmetic and simple variables inline, and costs nothing.
Read that two ways at once. It legitimizes the format for millions of people who’d never have searched for a third-party calculator, which grows the pool of people who eventually want more depth. It also removes the easiest sell dedicated apps had. “You can type math as a sentence” is no longer a differentiator. What’s left, deep unit libraries, live currency rates, hotkey speed, and richer variable handling, is what a paid app now has to compete on.
| App | Design center | Symbolic algebra | Platforms | Best for |
|---|---|---|---|---|
| Numi | Hotkey speed, disposable sessions | No | macOS only | Fast one-off math with optional saving |
| Soulver | Persistent documents, sheets | No | macOS, iOS, iPadOS, Windows | Documents you return to daily, cross-device |
| Calca | Markdown plus algebra | Yes | macOS, iOS | Solving for unknowns inside a text file |
| Apple Math Notes | Built-in, zero friction | Limited | macOS, iPadOS | Simple arithmetic without installing anything |
| Parsify | Extensible via plugins | No | macOS | Custom functions and developer-oriented extensions |
Feature depth inside each row varies more than the row suggests. Currency support can mean a short list of majors refreshed occasionally or dozens of currencies on a schedule measured in hours. Unit coverage can stop at length, weight, and temperature or extend into data, pressure, and energy. None of that is visible from a feature list. It becomes visible the first time you type the specific conversion you need.
Feature comparisons in this category mislead because the apps overlap on roughly ninety percent of what anyone actually types. The useful question is how you’ll use it.
Most people fall into the first two, and the honest answer is that either choice works. The measurable difference in my own use was time-to-first-keystroke: a hotkey-summoned window from any app, roughly a second, against opening a document-based app from the Dock and clicking into the right sheet, closer to five. That gap only matters if you do it thirty times a day, which is exactly the case where it compounds into something real.
In practice these apps eat three habits. The first is the browser tab left open on a converter site, which is slower than typing the conversion and sends your numbers to someone else’s server. The second is a throwaway spreadsheet created for four numbers and never opened again. The third, and the largest, is doing the math in your head and being slightly wrong.
The third one deserves emphasis because it’s the case people don’t notice. Small worded calculations, a tip, a discount, a rough transfer time, are just annoying enough on a traditional calculator that many people estimate instead. A text calculator for Mac lowers the cost of the calculation below the cost of guessing, which changes how often you bother.
Four limits, stated plainly.
Rounding deserves a mention too. Most apps in the category display a rounded result while carrying full precision internally, which is the correct behavior, but the display setting is usually global and easy to overlook. For invoicing or tax work, check it before trusting a total to the cent.
rent, rate, deposit.Step five is the actual test. Plenty of people enjoy the typing experience and never save anything, which is fine but means a calculator notepad app is doing half of what it could. The reuse is where it stops competing with Spotlight and starts competing with spreadsheets.
A calculator notepad app is a text editor that computes as you type. Each line holds a plain-text expression and shows its result beside it, and lines stay editable, so a calculation becomes a small document rather than a single disappearing number. Numi app, Soulver, and Calca are the established macOS examples.
A normal calculator holds one running value and forgets everything else. A calculator notepad keeps every line visible and editable, so you can change an input near the top and watch dependent totals below it update. It also parses units, currencies, and worded operators that a button calculator has no way to accept.
Partly. The Math Notes feature in Apple’s Calculator app solves expressions written inline in a notes-style document, covering basic arithmetic and simple variables. It doesn’t match dedicated apps on currency depth, unit coverage, or hotkey speed, but it handles the simplest cases without an install.
Yes, in every app in this category. The usual pattern is named input variables at the top and math below them, then editing only the inputs on each reuse. That turns a one-off calculation into a lightweight template without a spreadsheet’s structure.
Once a calculation has genuine interdependency across dozens of rows, or needs sorting, filtering, charting, or shared editing, a spreadsheet wins clearly. Calculator notepads are linear documents, and past roughly fifty lines the lack of structure becomes a liability.
The post Calculator Notepad Apps: The Full Guide (2026) first appeared on Pinturas Ribo.
]]>The post Why Menu Bar Icons Disappear Behind the Notch (and How macOS Decides) first appeared on Pinturas Ribo.
]]>macOS never draws menu bar content in the notch region, so when the frontmost app’s menus on the left and your status icons on the right need more width than the two strips beside the notch provide, macOS silently stops drawing whatever doesn’t fit. There is no overflow arrow, no hidden tray, and no notification. The app is still running. Its icon is simply not being drawn, and the number of icons you lose changes depending on which app is frontmost.
Key takeaways
Most explanations of this problem describe it as macOS dropping icons right to left. That’s close enough to be useful and wrong enough to mislead, because it suggests the outcome depends only on how many status icons you’re running. It doesn’t.
The menu bar is a single strip divided by a hard obstacle. The Apple menu and the active app’s menus claim the left side, status icons claim the right, and the notch sits in the middle as a wall macOS refuses to draw across. Those two zones compete for one shared pool of horizontal space. When the combined width exceeds what’s available beside the notch, macOS resolves the conflict by dropping icons that don’t fit, with no indicator at all.
This explains the behavior that otherwise looks random. An app with long menus can push half your icons out of existence while it is frontmost. Your icon count didn’t change. The app menus on the other side of the notch grew, and the status icons lost the argument.
Other parts of macOS handle overflow gracefully. NSToolbar has shown an overflow chevron for years. The menu bar does not. When macOS runs out of room it does not show an overflow arrow, does not give you a hidden tray, and simply stops drawing items that do not fit, which is why the icon isn’t missing so much as invisible.
Developers can’t compensate for this either, and it’s worth knowing that the app isn’t at fault. There is no API for an app to tell whether its icon is hidden: NSStatusItem.isVisible reports whether the app or user wants the icon visible, and returns true even when the icon is hidden in the notch or behind a menu title. Every menu bar developer fields the same support emails as a result, from users convinced the app stopped working.
Worth stating plainly since it affects how you should think about the fix: this is a macOS design gap, not something the app you installed did wrong. The problem predates the notch and affects any Mac running enough status items, but more people encounter it now because the notch reduces menu bar capacity.
Before changing settings, spend ten seconds confirming the diagnosis, because the fix for a crashed app is different from the fix for a clipped icon.
This diagnostic is useful but not a workflow. Switching apps to reach a VPN toggle isn’t a fix, it’s evidence.
These are ordered from least invasive to most, and the order matters: the first two are free, built into macOS, and solve the problem for most people without installing anything.
This is the highest-yield fix and the most commonly skipped. Open System Settings → Control Center and set items you rarely click, Spotlight, Siri, Sound, Wi-Fi, Bluetooth, Battery, AirDrop, to show in Control Center rather than the menu bar. Each one you relocate frees width for a third-party icon that genuinely needs to stay visible.
The tradeoff is real: a Wi-Fi icon moved into Control Center is one click further away, and if you toggle Wi-Fi constantly, keep it. The question worth asking per icon is whether you look at it or click it. Items you only click belong in Control Center. Items you glance at, battery percentage, a clock, a live number, belong in the bar.
Hold Command and drag any menu bar icon left or right. Put the items you most rely on close to Control Center and the clock, where macOS is least likely to clip them.
Be clear about what this does and doesn’t accomplish. Reordering does not create new space; it only decides which icons survive when the menu bar gets crowded. Treat it as setting priority, not as a fix on its own. Pair it with step one.
The least popular advice and the only one that actually creates capacity. A menu bar accumulates items the way a desktop accumulates files, and the audit worth running once a quarter is which icons you looked at in the past week. Anything you can’t remember using is a candidate for quitting or disabling at login.
If you legitimately need more items than the bar can hold, a manager is the correct answer rather than a workaround. Ice, Bartender, and Hidden Bar each collect overflow into an expandable section so you can reach icons macOS would otherwise drop. Hidden Bar is free and extremely lightweight, providing a chevron to expand and collapse extra icons, with control over which are always shown.
Verify current details before choosing one, since pricing and feature sets in this category change. One thing worth knowing in advance: some managers rely on screen recording permissions to dynamically show and hide overflowed items, which triggers the macOS privacy indicator in the menu bar. That indicator appearing frequently is a documented annoyance with this approach. Setup for each is covered in our guide to using CoinNotch with Bartender and Ice.
| Method | Creates new space | Requires an install | Setup time | Main tradeoff |
|---|---|---|---|---|
| Move icons to Control Center | Yes | No | 2 min | Relocated items take one extra click to reach |
| Command-drag to reorder | No | No | 1 min | Sets priority only; the bar’s capacity is unchanged |
| Quit unused utilities | Yes | No | 5 min | You lose the functionality you removed |
| Menu bar manager | No, but makes overflow reachable | Yes | 10 min | Another app to maintain; some use screen recording permission |
| Use an external display | Yes | No | n/a | Only helps when docked; built-in screen is unchanged |
—
A price ticker is more exposed to this problem than a typical icon, for a reason worth understanding before you blame the app. A standard status icon occupies a fixed, narrow width. A ticker renders variable-width text, and a wider string, a longer price, an added percentage change, a second coin, consumes more of the contested space than a glyph does.
The practical consequence: a ticker configured to show three coins side by side is a much larger overflow risk than one showing a single number, and on a 13-inch Air the difference decides whether it survives when you open a menu-heavy app. CoinNotch offers cycle mode partly for this reason, rotating through a watchlist in one narrow slot rather than claiming width for each coin at once.
The honest limitation: CoinNotch cannot detect when macOS has clipped its own icon, because no public API reports that. If the ticker vanishes after you open Xcode, the app has no way to tell you why, and it isn’t going to warn you. That’s a platform gap rather than an oversight, and it applies equally to every menu bar app you run.
Whether you use CoinNotch app for live crypto prices or CoinNotch mac for quick glances, the menu bar is where it belongs.
macOS never draws menu bar content in the notch region. When the active app’s menus on the left plus your status icons on the right need more width than the strips beside the notch provide, macOS silently stops drawing the items that do not fit. The apps are still running.
Not directly. macOS provides no overflow arrow, hidden tray, or indicator that icons were dropped. The reliable tell is that an app is running but its icon is gone, and quitting another app or switching to Finder makes it reappear.
Apps with many menu titles consume more of the left side of the menu bar while they are frontmost. That leaves less room for status icons on the right, so a menu-heavy app can push several icons out of view that were visible moments earlier under Finder.
No. Holding Command and dragging icons only changes which items survive when the bar runs out of room. It decides priority, not capacity. Creating actual space requires removing icons or moving system items into Control Center.
The notch makes it far more common but did not create it. Menu bar overflow predates notched Macs and affects any Mac running enough status items. The notch reduces usable bar width, so the ceiling arrives sooner on a 14-inch or 16-inch MacBook Pro.
No reliable API exists for this. NSStatusItem.isVisible reports whether the app or user wants the icon shown, and returns true even when the icon is clipped behind the notch, so developers cannot warn you that your icon has been dropped.
Menu bar behavior around the notch has shifted across releases, and macOS 26 Tahoe moved several relevant settings into a redesigned Control Center panel while changing how the bar renders. If icons started disappearing after an OS update rather than after installing something new, the cause is likely a change in the bar itself rather than in your app selection, and our guide to what Tahoe changed for menu bar apps covers what moved where. For the broader question of what deserves that space in the first place, see our guide to what the MacBook notch is actually for.
This article is for information only. It is not financial, investment, or tax advice. Crypto assets are volatile and you can lose everything you put in. CoinNotch displays public market data and does not trade, hold funds, or connect to any account.
The post Why Menu Bar Icons Disappear Behind the Notch (and How macOS Decides) first appeared on Pinturas Ribo.
]]>The post Rectangle’s Command Line Interface: A Guide for Power Users first appeared on Pinturas Ribo.
]]>The short version: Most people never need it, but Rectangle app has a companion command line tool that lets its snap actions be triggered from the terminal — useful for scripting, chaining into shell workflows, or calling from other programs. It’s a niche feature aimed squarely at people already comfortable in the terminal, not a replacement for keyboard shortcuts in day-to-day use.
The Rectangle CLI is a separate command line companion to the main app — it doesn’t replace the GUI or the keyboard shortcuts, it adds another way to trigger the same snap actions, this time from a terminal command instead of a key combination. It communicates with the running Rectangle app rather than duplicating its logic, so the main app still needs to be installed and running for the CLI to do anything.
This is aimed at a specific audience: people who already script parts of their macOS setup, use the terminal as a primary tool, or want to trigger window arrangements from something other than a keypress — a shell script, a scheduled task, or another command line program that needs to arrange a window as part of a larger job.
The CLI is typically installed separately from the main app, commonly through Homebrew for people who already manage their command line tools that way. Because it’s a companion to the GUI app rather than a standalone replacement, the main Rectangle app needs to already be installed and running with Accessibility permission granted — the CLI is a messenger, not an independent window manager.
Once installed, the general pattern is a command followed by the name of the action you want — the equivalent of whatever a keyboard shortcut would trigger, like snapping left, maximizing, or moving to the next display. The exact command names and syntax are documented on Rectangle’s own site, and it’s worth checking the current documentation directly rather than an old example, since command names have occasionally changed between versions.
A single command run manually in the terminal isn’t faster than a keyboard shortcut — that’s not the point. The value shows up once that command becomes one line in something bigger.
Shell scripts. A setup script that opens a project, launches an editor and terminal, and arranges both windows in one run can include a Rectangle CLI call as its final step, turning several manual actions into a single script execution.
Conditional logic. Because it’s a terminal command, it can sit inside an if-statement or loop in a script — snap a window only if a certain condition is met, something a static keyboard shortcut has no way to express.
Integration with other command line tools. For people already gluing together several command line utilities to manage their environment, the Rectangle CLI slots in as one more piece — callable from cron jobs, other scripts, or tools that themselves shell out to run commands.
Rectangle also supports a URL scheme usable from Apple’s Shortcuts app, which serves a similar goal — triggering snap actions outside of keyboard shortcuts — through a different mechanism. The CLI fits naturally into terminal-based and shell-script workflows; the Shortcuts integration fits naturally into Apple’s own automation ecosystem, including Siri and scheduled Shortcuts automations. Which one makes sense depends entirely on where the rest of your automation already lives — there’s no reason to use both for the same task, just whichever matches the tools you’re already comfortable in.
To be direct about it: almost everyone. Rectangle’s keyboard shortcuts and drag-to-snap cover the overwhelming majority of daily window management, and the CLI adds nothing for that use case — it’s strictly slower to type a terminal command than to press a shortcut you’ve already memorized. This feature exists specifically for the smaller group of people who are already scripting their environment and want window arrangement to be one more thing a script can do, not a general recommendation for typical use.
What it is — A terminal companion to the main Rectangle app, not a replacement.
Requires — The main app installed, running, and with Accessibility permission already granted.
Best for — Shell scripts, conditional logic, integration with other command line tools.
Not needed for — Normal day-to-day window snapping; shortcuts are faster.
The Rectangle CLI is a small, well-targeted feature for a specific kind of user — someone already comfortable scripting their Mac who wants window arrangement to be one more command they can call rather than a manual action. For everyone else, it’s safe to ignore entirely; keyboard shortcuts remain the faster and more natural way to use Rectangle day to day.
Whether you use Rectangle app with CLI or Rectangle mac for shortcuts, both make window management effortless.
Yes, a companion command line tool exists for Rectangle that lets its window actions be triggered from the terminal rather than only through keyboard shortcuts or the app’s own UI, useful for scripting and integration with other tools.
It’s typically installed separately from the main Rectangle app, often through Homebrew, and requires the main Rectangle app to already be installed and running since the CLI communicates with it rather than replacing it.
The CLI is most useful for scripting: triggering a snap action as one step in a shell script, calling it from another program, or combining it with conditional logic that a static keyboard shortcut can’t express on its own.
No. The vast majority of Rectangle users never need it, since keyboard shortcuts and drag-to-snap cover normal daily use. The CLI is aimed specifically at people scripting their environment or integrating window management into other tools.
The post Rectangle’s Command Line Interface: A Guide for Power Users first appeared on Pinturas Ribo.
]]>