Google Ads Editor download for Mac: what it does not cover

The download is the easy part. One file, no licence key, no account setup during installation, and the whole thing is finished before a kettle boils. The parts that cost time come after: whether the Mac meets the floor, which half of the daily job the installed application actually covers, and what to do about the half that never leaves ads.google.com. Anyone downloading this expecting to close the browser tab is going to be disappointed, and it is better to know that before rearranging a workflow around it.

What arrives when the download starts

Google Ads Editor is a free, downloadable application for managing Google Ads campaigns. The download link on the Ads Editor product page hands over a single disk image from dl.google.com, named google_ads_editor.dmg. As of the current build the file is roughly 334 MB, which is large enough that a slow connection will notice, and it is one package rather than a choice between processor types. Opening the image and dragging the icon into the Applications folder is the entire installation.

There is no separate Apple silicon and Intel download to choose between, which removes a decision that trips people up with other tools. The same file serves both. Language is handled inside the application rather than at download time: the interface is offered in around forty languages, Japanese among them, and the setting can be changed after installation rather than being fixed by which page the download started from.

The first launch asks for a Google account and permission to access the Ads account. Newer builds handle that exchange in the background instead of asking for an authorisation code to be copied and pasted, which is what older documentation describes.

The line that decides whether this is even possible

One sentence in the system requirements settles it.

Google Ads Editor is available for 64-bit Windows 10 or later and MacOS 13 or later. Source: support.google.com

The floor is the operating system, not the processor. An Intel Mac running macOS 13 Ventura or later is supported. An Apple silicon Mac still on macOS 12 is not. That is the opposite arrangement to some other recent releases, where the chip decides and the OS version is secondary, so it is worth checking the actual version in About This Mac rather than assuming a recent purchase qualifies.

This matters more each year. Vendors keep lifting the minimum macOS version on desktop applications, and a Mac deliberately held back for a plugin, an audio interface or an internal tool eventually finds that the desktop version of a service is closed to it while the website remains open. For an advertiser in that position, the browser is not a fallback. It is the whole product.

What the installed application covers, and what stays online

The basic loop is straightforward. Download one or more accounts, edit offline, then post the changes back. Around that loop sit the reasons people install it: bulk edits across many campaigns, search and replace across ad groups, copying or moving items between campaigns and accounts, editing several accounts in the same session, working in draft before posting, and undo across a long series of changes.

The gaps are documented rather than hidden, and they are the useful part of this article.

Task	In the installed application	Where it is done otherwise
Bulk keyword and ad edits	Yes	Either
Shared creatives	No	Google Ads online
Shared budgets	Read only	Google Ads online
Creating an Ad gallery ad	No, existing ones can be copied	Google Ads online
Creating an app promotion ad	No, existing ones can be copied	Google Ads online
Campaign experiments	Status updates only	Google Ads online
Recommendations, billing, account settings	Not covered	Google Ads online

Read the right hand column as a description of a normal week. Even for an advertiser who lives in Editor, several tasks each week send them back to the browser, and account level work stays there permanently. The installed application is a bulk editing tool with an offline cache, not a second copy of the platform.

Offline most of the time, and what that implies

The security documentation is unusually specific about when the application talks to Google: when downloading account data, when posting edits, and when checking for updates, which happens on startup and every twenty five hours of continuous use. Outside those moments it is offline.

That design has three practical consequences. The statistics shown next to a campaign are from the last download, so a number that looks wrong is often simply old. Two people editing the same account in separate copies will not see each other, which is why a download immediately before a big edit is worth the wait. And the account structure sits on the local disk between sessions, which is convenient on a personal machine and worth thinking about on a shared or departing one.

None of that is a fault. It is the trade that makes bulk editing fast on a laptop with a poor connection. It just means that the browser side is where anything live happens, and the browser side is exactly where most advertisers have never organised anything.

The problem the download does not solve

Installing Editor cleans up bulk edits. It does nothing about the other half of the day, which for most people looks like this: one browser window, a Google Ads tab, a manager account, a client account signed in through it, an Analytics tab, a Merchant Center tab, and a personal Google session that keeps stealing the login.

Account switching is the tax. Every switch is a redirect, a password manager prompt, sometimes a two step verification, and a lost place in whatever was being read. For an in house team with one account it is a nuisance. For anyone holding several client accounts it is a daily cost measured in minutes rather than seconds.

There is a second, quieter cost. When every account shares one browser session, the account currently signed in is invisible until a page loads. Reports get pulled for the wrong client, a budget gets edited in the wrong account, and the mistake is only obvious afterwards. Browser profiles solve part of this, but they live inside the browser: switching profile still means finding the right window among identical windows, and the profiles disappear from view the moment the browser is quit.

A site to app tool addresses that specific tax. The mechanism is worth understanding: instead of shipping its own browser engine, it builds a small application bundle that points, through a symlink, at a Chromium browser already installed on the Mac. Chrome, Brave, Edge, Opera, Vivaldi, Chromium and Arc can each be the base, and because the link references the real binary, updating the browser updates every window built on it. Each generated app carries its own profile, so a window signed into one Google account stays signed in while another window holds a different one. Notifications, Dock presence and the tab bar are switches set when the app is made, and the option by option reference for those switches is in the Guide.

Two options fit advertising work particularly well. URL rules can restrict a window to an allow list, so a window built for ads.google.com stays on it and does not become another general browser. And the ready made catalogue means the URL, name and icon for a service are already paired, with more than three hundred entries listed on the Supported services page.

The limits are worth stating plainly. A window built this way is still the web interface. It does not gain the bulk editing tools, it does not work offline the way the installed application does, and it does not replace the download. It changes where the web interface lives and which account it holds, and nothing else.

Splitting the day between the two

Once both halves are set up, the routine sorts itself into three blocks, and naming them stops the drift back into a single overloaded browser window.

The first block is the morning read. Performance, spend against budget, disapprovals, recommendations and anything flagged overnight all live in the web interface, and none of it requires editing. This is the block that belongs in a dedicated window, because it happens every day at the same time and always in the same account.

The second block is bulk work. Download the account first, make the edits offline, and post them in one go. Grouping edits this way is not just tidiness. Every post is a write to a live account, and a single deliberate post is easier to review, easier to explain to a client and easier to undo than fifteen scattered ones.

The third block is the part that only exists online: creating the formats Editor cannot create, adjusting shared budgets, touching billing or account settings, and anything involving assets shared across campaigns. Keeping this block in the same dedicated window as the morning read means the account signed in is already the right one.

The failure mode is skipping the download step in block two. Edits made against a stale local copy either overwrite someone else's work or fail on posting, and both outcomes cost more time than the download would have taken.

Files, updates and removal

Two housekeeping details save trouble later.

Updates are checked at startup and roughly once a day during long sessions, which means a Mac that is never restarted can run an old build for a while. Features that appear missing are sometimes a build behind. Quitting the application and reopening it is the fastest way to force the check, and it is worth doing before concluding that a campaign type is unsupported.

Disk use is the other thing worth noting. The download itself is large, and the account data cached after each download adds to it, growing with the number and size of the accounts kept locally. On a laptop with a small drive, an agency holding a dozen client accounts will feel it.

Removal is not just a matter of dragging the icon to the Trash. Google's documentation lists the folder and file that hold local data, at ~/Library/Application Support/Google/Google-Google Ads-Editor and ~/.config/Google/Google-Google Ads-Editor.ini. Deleting the application alone leaves the downloaded account structure on the disk. Removing both gives a clean reinstall, and on a machine that is changing hands it is the step that actually removes client data.

What to set up first

Check the macOS version before anything else, because macOS 13 is a hard floor and nothing else in this article matters if the Mac is below it. Install the download and use it for what it is good at, which is bulk editing. Then give the browser side the same treatment by putting ads.google.com in its own window, one per account, with Kagemusha, which is free for the first three.