Six Months with Arc: The Browser That Almost Converted Me (And the One Thing That Didn’t)

The Honeymoon Phase Never Really Ended

Six months ago, I downloaded Arc with the kind of skepticism you bring to anything that promises to revolutionize your daily habits. I’ve been through enough productivity app cycles to know that enthusiasm usually crashes around week three, right around when you realize the friction of change outweighs whatever gains you were promised. But here’s the thing about Arc: it didn’t crash. It just quietly became how I browse.

I’m not going to pretend I’m some early adopter who figured this all out before it hit 4 million active users by mid-2025. I came in after the hype had already settled into something real. What I found was a browser that seemed to understand something fundamental about how I actually work, as opposed to how the internet wants me to work. There’s a difference, and it matters more than I expected.

The Spaces feature and the pinned tabs architecture are the parts people can’t seem to shut up about, and for once the hype isn’t undeserved. When 67% of people in a 2025 Hacker News poll said they couldn’t go back from these features, they weren’t exaggerating. I have a Space for work, one for writing, one for research, one for the chaos. They’re not just folders or bookmarks with fancy names. They’re actual separation of context. My brain treats them like different rooms in a house, and once you’ve organized your digital life that way, the tab bar chaos of traditional browsers feels genuinely barbaric.

The Pivot and the Weird Feeling It Gave Me

Then in January 2025, The Browser Company announced something that shifted the whole energy. The Browser Company Arc 2.0 announcement made it clear that Arc Search Desktop, an AI-first autonomous browsing agent, is where the company is putting all its chips now. Which meant Arc, the browser I’d grown attached to, was getting put into maintenance mode. No more major features. Just stability.

I don’t think this is a bad decision, necessarily. Companies have to pick a direction, and the future is clearly going somewhere AI-shaped whether we like it or not. But it produced this strange, small grief in me that I didn’t expect. I’d finally found a browser that felt like it was designed for humans first, and now it was going to be left behind while the company chased the next thing.

That’s when I started noticing the cracks. Not in Arc itself, but in my relationship with it. The Spaces were still perfect. But I started paying attention to other things. The search functionality. The integration with everything else I use. The small quality-of-life moments you don’t think about until they’re missing.

The Thing I Couldn’t Fix, So I Cheated

Here’s where I get honest: I went back to Chrome for one specific, somewhat embarrassing reason. Research synthesis. I do a lot of reading across multiple sources and then need to pull it all together, and Chrome’s bookmarking and research features, combined with its extensions ecosystem, just work better for this particular workflow. Arc felt like it was fighting me on it. Chrome felt like it was built for exactly this.

I felt weird about it. Like I’d betrayed something. And maybe that’s silly, but it forced me to confront something I’d been avoiding: I didn’t switch to Arc out of principle. I switched because it made my life better in concrete ways. But that same pragmatism meant I couldn’t stay when another tool did one specific thing better. The loyalty I felt to Arc was real, but it’s not stronger than the friction of working around its limitations.

The statistic that keeps nagging at me is this one: Chrome still holds 65.7% of the global browser market share as of 2025. All the Chromium-based challengers combined, including Arc, account for less than 8%. Which means most people never even consider stepping away from Chrome, let alone actually do it. And then when they do, like I did for that one thing, there’s usually a reason. Chrome’s dominance isn’t just momentum. It’s because it’s genuinely, frustratingly difficult to build something better at everything.

Why This Matters More Than Browser Wars

The reason I’m writing this is because Mozilla Internet Health Report 2025 flagged something that should worry us more than it does: four of the top five browsers now run on Chromium. That’s not just a market share thing. That’s a monoculture thing. It means that when Google makes a decision about how the web should work, it’s not really a choice anymore.

Arc tried to matter against that. The Browser Company built something genuinely thoughtful, actually different in the ways that count. And it worked for me, until it didn’t. Not because Arc failed, but because changing one thing in your entire digital workflow takes more friction tolerance than any one feature advantage can overcome. That’s not Arc’s fault. That’s the geometry of the problem.

I still use Arc. The Spaces are still there. I’m in no rush to leave. But I’m also back in Chrome for that one thing, and I’m not going to pretend that means nothing. It means the incumbents win not because they’re always better, but because they’re already there, and that’s often enough. What I’ve learned is that changing your mind about a product doesn’t make you fickle. It makes you honest about what you actually need versus what you thought you needed. Sometimes those are different things.

If you’ve got a different experience with Arc, or if you’ve found a research workflow that actually works better, I want to hear about it. These things matter more when we’re actually comparing notes instead of just defending territory.