Shift browser: what it does and where it breaks down

Searching the name returns two different products wearing it. One is the older v9 build that most written reviews describe. The other is a rebuilt browser that has been rolling out to existing users over recent months and that carries different limits, a different layout model and a different relationship between accounts and containers. Understanding what the product is means separating those two first, then looking at what the design covers and where it stops.

Three units, and only one of them is hard to replace

The interface is assembled from three things, and they are worth naming separately because they carry very different weight.

The first is the Space. It is a container for a context: work, study, a client, a hobby. The published description frames it against ordinary browsers, which force multiple accounts and unrelated browsing into one rigid structure. Inside a Space, signing into the same service under a second account does not require signing out of the first.

The second is the app. A web service such as Gmail or Slack is registered as a permanent resident rather than a tab, added from a library in one click. Two entry points exist: the app icon showing three squares with a plus, and the plus sign that sits by default on the Spaces and apps bar.

The third is the layout. Bars, apps and controls are dragged into position, and a set of templates provides starting points, including one arrangement that pins apps and Spaces to a sidebar for fast context switching.

Only the first of these is genuinely hard to reproduce elsewhere. Layout can be approximated with window management. Permanent residency can be approximated with pinned tabs. Keeping two accounts of the same service signed in at once requires separated cookie storage, and no amount of arranging tabs produces that.

What sits underneath

The product is built on Chromium, and the documentation says so directly when explaining Mac system requirements. That single fact determines most of the boundaries.

Extension support follows from it: almost every extension in the Chrome extension library is supported. Password handling follows too, with credentials encrypted and stored locally for autofill, plus a checkup that flags duplicate or weak passwords. Anyone already depending on a password manager extension or a content blocker can assume it transfers.

Platform support is Windows 10 and 11 plus Mac, with macOS 11 Big Sur or newer required and at least 8GB of RAM recommended. There is no mobile build, and the help entry on the subject states plainly that availability is limited to those desktop platforms.

The count of supported services is published inconsistently. The apps directory page claims integration with over 4,500 apps, while the corresponding help entry says over 1,500. The more useful detail than either number is the request mechanism: services missing from the library can be submitted for addition, which matters more than the headline figure for anyone whose daily tools are regional or niche.

Two versions answer to the same name

The transition between builds is the single biggest source of confusion in anything written about this product, including older review articles that are still ranking.

	v9	Rebuilt version
Layout	Fixed structure	Drag and drop bars, apps and controls
Spaces	Each Space tied to an email account	No email account required per Space
Appearance	Standard	Eight colour themes across light and dark
Apps and Spaces model	Present	Carried over with changes

The second row is the one that changes how the tool is used. Under v9, containers effectively organised themselves around mailboxes, so the setup was built mailbox first. Without that constraint, Spaces can be cut by role, client or project, which is a different mental model even though the feature name did not change.

Migration terms are published. The rebuilt version reaches existing users automatically over a period of months and carries Spaces, apps and bookmarks across. Downloading it early is permitted and explicitly described as starting from a clean slate with nothing migrated. Paying users moving early are told to sign in with the primary account email so the paid entitlement follows them.

Checking which build is installed takes one step: the menu bar, then About Shift. A version number beginning with 9 is the older build, and any advice written for the other one will not match.

What the safety and sustainability features actually cover

Two features get prominent placement and both have published scopes, which makes them easy to assess without guessing.

Download scanning modifies the usual Chromium Safe Browsing path to add a file reputation service from Avira. The check happens before a file is written to disk, so a flagged file is quarantined by the browser rather than landing in the downloads folder. The documentation states that the suspected file is never inspected or transmitted by the browser itself, and that local antivirus still runs its own scan afterwards. It is available on both the free and paid tiers.

The Carbon Meter estimates emissions from browsing and offsets them through purchased carbon credits. The exclusion list is the informative part. It does not count local device power draw, background system operations unrelated to browsing, or cryptocurrency and AI workloads, and estimates are based on data transfer size rather than client side processing. Using a VPN can skew the result because the region becomes unclear.

A built in AI assistant sits alongside these, described as available in place rather than in a separate tab, with limited usage on the free tier and expanded usage on the paid one. It is the kind of function that an external tool replaces without difficulty, so it belongs in the description of the product rather than in the reasons to choose it.

What the layout model asks of the person setting it up

One characteristic separates this design from a browser that simply remembers pinned tabs, and it is easy to miss in a feature list: the arrangement is not supplied, it is authored. Bars, controls and apps start from a template and are then dragged into whatever positions suit the work, which means the quality of the result depends on decisions made by the person building it.

That has an upside and a cost. The upside is that a layout can mirror how attention actually moves during a day, with the two or three services checked constantly kept visible and everything else one level down. The cost is that a setup assembled quickly, by adding each service at the moment it was first needed, tends to grow into the same undifferentiated pile the tool was adopted to avoid. Nothing in the product prevents that outcome.

The templates exist as a hedge against it. Starting from a published arrangement, such as the one that pins apps and Spaces to a sidebar, gives a structure that has been thought through before the first service is added. Adjusting a working arrangement is considerably easier than designing one from an empty window, particularly during the first week when the shape of the routine is not yet obvious.

A second consequence shows up after migration. Because the rebuilt version removed the requirement to associate an email account with each Space, a layout copied mentally from a v9 setup will reproduce a constraint that no longer applies. Rebuilding the container list from scratch, based on which identities actually need separating, produces a shorter list than the one carried over.

Where it breaks down

The failure points are not missing features. They are mismatches between how the product is built and how a particular routine works.

• No mobile build. A workflow that continues on a phone leaves the product entirely at that boundary, and no tier changes that.
• One account per subscription. Multiple machines are handled by signing in and enabling sync from Quick Settings and then Advanced Settings, which is different from two people sharing one licence.
• Links from outside the window. A link clicked in a mail client or a chat app is handed to whatever macOS treats as the default browser. If that is not this application, links keep landing in the wrong account regardless of how carefully Spaces are arranged.
• Memory grows with separation. Each isolated session runs its own processes with its own cookie store, which is exactly the mechanism that keeps accounts apart. More containers means more resident processes, and that cost belongs to the isolation itself.
• Automatic launch. Startup behaviour is configurable under Quick Settings, then Advanced Settings, then the OnStartup tab, where opening on login and opening on wake are separate switches. Anyone who found the application running without asking for it should look there first.

There is also a distribution detail worth knowing, because it generates a recurring question. A dedicated help entry, written for people who find the browser installed without remembering installing it, explains that in house apps such as Recipes, Manuals and Games are integrated into the browser rather than being standalone, so installing one of those installs the browser. That, along with downloads from the official site or affiliate pages, accounts for most cases of an unexpected appearance.

Who runs it, and where it is distributed from

The footer on every page states that the company is B Corp certified as part of the Redbrick portfolio. The about page places headquarters in British Columbia, Canada, and claims 2.4 million users along with a figure of four hours returned per week, which is a marketing estimate rather than a measurement anyone else can verify.

The distribution address has moved. The former domain tryshift.com returns an HTTP 301 permanent redirect to shift.com as of September 2026, so old bookmarks and older articles still resolve. The practical consequence is about numbers rather than availability: a page written for the old domain is likely to carry the old pricing and the old limits, and a reader comparing figures across sources will find contradictions that come from the date of writing rather than from error.

No notice of discontinuation or of closing new signups appears anywhere on the current site. What is in progress is the version transition, not a wind down, and the free download remains available without an account and without a card.

What to change first

Answer three questions before installing anything: whether two accounts of the same service need to be open at once, how many services genuinely need a permanent home rather than a tab, and whether any of this has to continue on a phone. A yes to the third rules this category out on its own. If the first two produce small numbers but the switching between them happens dozens of times a day, the cost sits in the switch rather than in the container count, and giving each app a real window with its own icon in the app switcher addresses a different part of the problem: that approach is described on Features and on Workspaces, with a direct point by point look at the product covered here on Compared with Shift and the tool SpaceDeck listing what can be dropped in without configuration.