Backblaze download on a Mac: the backup console in one window

Unlike most searches that end at a download page, this one ends with something real. Backblaze publishes a native Mac client, it installs in a couple of minutes, and after that it mostly disappears. Which is exactly when the second search starts, because the moment a file has to come back, the client is not where the work happens. Restores, version history, sharing a single file, finding a stolen laptop and billing all live on the Backblaze website. The installer answers one question and creates another, and the second one is the one worth planning for.

What the download actually installs

Backblaze is explicit that the desktop side is native rather than a bundled browser or a Java wrapper, and it lists that as a deliberate design choice.

Native Mac and Windows clients, no Java or middleware. Built native to be reliable, and light on both system and disk. Source: backblaze.com

What arrives is a background service and a settings panel, and the design goal is that neither needs attention. The published price for Computer Backup is $9 per month, $99 per year, or $189 for two years, which the site presents as $8.25 and $7.88 per month equivalents on the longer terms. The trial is 15 days with no credit card required. Those numbers are per computer, which is the thing to hold on to when a household has three Macs and an external drive on each of them.

The client's scope is narrow by design. It selects what to exclude, it throttles, it reports progress, and it uploads. It is not a file browser, it is not where versions are compared, and it is not where a restore is assembled. Reading the product that way makes the rest of this article obvious: the desktop app is the sending half, and the website is the receiving half.

Everything you do in an emergency happens in a browser

Signing in at the Backblaze site is what stands between a person and their files. Backblaze's published feature list for personal backup covers, among other things, restoring from web, mobile or a shipped hard drive, sharing individual files that have been backed up, and locating a lost or stolen computer. None of those is a function of the installed client. All of them are pages.

The restore path has a documented shape that explains why this matters.

Web-based restores. Zip restores up to 500GB per request with ability to prepare multiple restores. Source: backblaze.com

So a large recovery is not one click. It is a set of requests, each prepared on the server, each becoming available at a different time, each downloaded through a browser that has to stay signed in and awake while it happens. The alternative for very large recoveries is physical: Backblaze ships an encrypted USB drive, and its own description says the drive is free upon return within 30 days, which is a refund arrangement rather than a rental. Either way the ordering, the tracking and the return are all done on the website.

The uncomfortable part is when this happens. A restore is requested on the worst day of the quarter, often on a borrowed machine, often while somebody is waiting. That is the least good moment to be hunting for a tab, re-finding a sign in page, and working out which of three prepared archives is the one that contains the folder.

The three places Backblaze lives on a Mac

	Installed client	Website in a browser tab	Website in its own window
Runs the backup	Yes	No	No
Restores and version history	No	Yes	Yes
Share a single backed up file	No	Yes	Yes
Locate a lost computer	No	Yes	Yes
Billing and plan changes	No	Yes	Yes
Where you find it	Menu bar and System Settings	One of many tabs	Dock, Spotlight, Cmd+Tab
Survives quitting the browser	Not applicable	No	Yes

Read down the middle column and the pattern is clear. Every row that involves getting data back, or proving that data is there, belongs to the browser. That is not a criticism of the client. It is how a backup service with a web console is put together, and the same split exists on Windows.

What follows from it is a small decision most people never make deliberately. The console either lives in the general browser, mixed in with everything else, or it gets a place of its own.

Why the console is a bad fit for a general browser tab

Three things about the console make a shared browser awkward.

The first is duration. Preparing a restore is a server side job, and the page that tracks it is open for a long time doing nothing. In a browser with forty tabs, a page that sits idle for an hour is the kind of page that gets closed by accident, reloaded during a cleanup, or lost when the browser is restarted to fix something unrelated. The consequence is not data loss, but it is repeated sign ins and repeated re-navigation at the exact moment that is most expensive.

The second is authentication. Backblaze offers two factor verification by TOTP and SMS, and an optional private encryption key that has to be supplied before a restore can be decrypted. Every one of those steps is a form in a browser, and forms in a browser are affected by whatever else is installed in that browser. A password manager extension, a form filler, a privacy extension that blocks a script the sign in flow depends on: any of them can turn a two minute sign in into a fifteen minute diagnosis.

The third is separation of concerns. The account that can restore every file from a Mac is also the account that can see the file names on that Mac. That is a different class of login from a news site or a shopping cart, and keeping it in the same browser profile as fifty extensions is a choice rather than a default, even if nobody framed it as one.

The cheapest version of the fix

macOS ships with a way to give a website its own window, and Apple's documentation states what the result is.

A web app functions independently of Safari. It shares no browsing history, cookies, website data, or settings with Safari. Source: support.apple.com

The path is File then Add to Dock in Safari, and the app that comes out is saved to the Applications folder of the home folder, appears in Spotlight, and can be given its own name, icon and starting URL from its own Settings window. For a backup console this is close to ideal, because the console is a single site with a single login and no need for tabs.

Where that route runs out is engine choice and extensions. A Safari web app runs on Safari with Safari's extensions, which is a limitation in general and occasionally an advantage here, since a page that handles encryption keys is a reasonable page to run with nothing extra loaded into it. A site to app tool built on a Chromium browser is the other direction, useful when a password manager or a specific extension has to be present, and when each window needs its own isolated profile so that a work account and a personal account can both stay signed in.

The private key is the reason to take the window seriously

Backblaze's published security description is worth reading before deciding where the console lives. The service uses 2048 bit public and private keys to secure a symmetric AES-128 key for all data, and offers the option to additionally encrypt everything with a private key that the account holder supplies. That option is the difference between a service that can produce your files and a service that cannot produce them without you.

It also changes the restore. With a private key in place, the key has to be entered on the Backblaze site at restore time, which means the most sensitive string in the whole arrangement gets typed or pasted into a browser window. Deciding in advance which window that is, and what else is loaded into it, is a small act of hygiene that costs nothing and is impossible to do retroactively.

Version retention is part of the same picture. Backblaze lists extended version history with an optional forever retention setting for an added fee, and the place that setting is changed is the account console rather than the client. So the console is not only the emergency tool. It is where the terms of the backup are actually set.

One window, or one window per account

Households and small studios usually end up with more than one Backblaze login. A personal account for the family Macs and a business account for the work machines is the common pattern, and Backblaze prices Personal and Business backup at the same published $99 per year, so there is no incentive to force everything into one.

Two logins in one browser profile do not coexist. Session cookies belong to the profile, so signing into the second one signs out of the first, and the usual workarounds are private windows that forget everything or separate browser profiles that produce a Dock of identical icons. Two windows, each with its own profile and its own icon, is the version of this that stays understandable at 11pm during a recovery.

The test for whether something deserves a window of its own is worth stating plainly, because it prevents the opposite mistake. A site earns a window when it has its own login, is needed on a schedule or in an emergency, and has a real cost attached to not finding it quickly. A backup console passes on the second and third counts even though it might be opened twice a year. A blog post about backup strategy passes on none of them. Ten windows in the Dock is not tidier than ten tabs, it is the same pile with better icons, so the supported services list is more useful as a filter than as a shopping list.

Three things to check on the first day

Sign in from the window and complete the two factor step, so the flow is known to work before it is needed. Prepare a small restore, a single folder, and confirm the download lands in the Downloads folder from inside the window. If a private encryption key is in use, confirm the key can be pasted in and the archive decrypts. The guide covers the setup itself, but those three checks are what make the window trustworthy rather than decorative.

What to change first

Install the client, then give the Backblaze account console its own window and sign in once so the two factor path is already proven. Do the small test restore today rather than during an emergency, and if a second Backblaze login has to stay signed in alongside the first, Kagemusha is one way to get per window profiles.