Arc Is Shutting Down: What to Do With Your Links, and the Best Arc Alternatives for Teams

Arc will stop working on Mac and Windows on December 22, 2026, after The Browser Company decided to focus on its AI browser, Dia (TechCrunch). If you are looking for an Arc browser alternative, you have good options, and most lists stop there. This one also looks at the part that hurts teams most: the links that lived in everyone’s Arc sidebar.

First things first: export what you have. Our step-by-step guide on how to export your Arc bookmarks before December 22 covers Arc’s built-in export, converting the sidebar file, and moving to Dia.

What to look for in an Arc replacement

Arc changed how people browse with a few ideas. Check each candidate against the ones you actually used:

  • A vertical sidebar of tabs instead of a tab strip.
  • Spaces that separate work, clients and personal browsing.
  • Pinned tabs and folders that behave like a lightweight bookmark manager.
  • Split view and a quick command bar.
  • Easy migration of what you already have.

No browser copies all of Arc. Pick the one that keeps the habits your day depends on.

The best Arc alternatives

Dia: the official successor

Dia is The Browser Company’s own browser, built around an AI assistant. It imports your Spaces, Favorites, pinned tabs and folders straight from Arc (Arc Help Center), and Arc features such as Profiles (formerly Spaces), optional vertical tabs and Pinned Tab Groups (formerly folders) carry over, with AI optional (TechCrunch).

Good fit if you want the shortest move and like the team behind Arc. Check Dia’s site for current platform support, since its Windows version is new.

Zen: the closest layout, built on Firefox

Zen is a free, open-source browser built on Firefox, with vertical tabs, workspaces and a compact, Arc-like layout. It runs on Mac, Windows and Linux.

Good fit if you loved Arc’s look and want an open-source, non-Chromium browser. Firefox add-ons work, Chrome extensions do not.

Vivaldi: the most configurable

Vivaldi is built on Chromium and lets you rebuild most of Arc yourself: vertical tabs, workspaces, tab stacks and a command bar, plus deep customization. It runs on Mac, Windows and Linux and installs Chrome Web Store extensions.

Good fit if you are happy to spend an hour setting things up exactly how you like.

Microsoft Edge: the safe choice at work

Edge has vertical tabs and Workspaces, but each Workspace opens in its own window rather than switching in place like Arc’s Spaces. It is often already approved by IT and fits teams on Microsoft 365.

Good fit if you need something your company will sign off on this week.

Google Chrome: the familiar default

Chrome offers tab groups and separate profiles, and every extension works. It is the least like Arc, but nothing about it will surprise anyone on your team.

Good fit if you want zero learning curve and will rebuild your organization elsewhere.

Quick comparison

BrowserBuilt onClosest to Arc inGetting your Arc links in
DiaChromiumProfiles, pinned tab groupsDirect import from Arc
ZenFirefoxLayout, workspacesBookmarks HTML file
VivaldiChromiumVertical tabs, workspaces, command barBookmarks HTML file
EdgeChromiumVertical tabs, workspaces in windowsBookmarks HTML file
ChromeChromiumTab groups, profilesBookmarks HTML file

The bookmarks HTML file comes from converting Arc’s sidebar file, explained in the export guide.

The real problem for teams: your links lived in a sidebar

Picking a browser is the easy part. The harder part is what Arc’s shutdown exposed: for many teams, the links that run the work lived in each person’s Arc sidebar. The dashboards, the client folders, the onboarding docs, the staging URLs.

That setup has three costs, and Arc’s end makes all of them visible at once:

  • Links are tied to one app. When the browser goes, everyone migrates their own sidebar, by hand, and some of it gets lost.
  • Links are invisible to teammates. Your pinned folder of release checklists helps nobody else.
  • Onboarding starts from zero. A new hire has to collect the same links that everyone else already has.

Switching browsers solves none of these. The next browser will have its own sidebar, and in a few years the same problem comes back.

Keep shared links in one place no browser owns

A better setup separates your browser from your team’s links. Linkinize is a bookmark manager for teams: shared workspaces, tags and instant search, synced to a browser extension. Links live in the cloud instead of in a browser:

  • Workspaces replace Spaces, shared with the people who need them: one per team, client or project. See multiple workspaces.
  • Search finds any link in a keystroke, from the extension or the web app. See search.
  • Everyone gets new links automatically, on every device they sign in to. See sync.
  • Switching browsers costs nothing next time. The extension is listed for Chrome, Edge and Firefox, and the web app works in any browser.

To move over, import the bookmarks HTML file from your Arc export into a workspace, then invite your team. If you are comparing dedicated bookmark managers too, our comparison pages cover the main ones, and best bookmark manager tools gives the wider picture.

Frequently asked questions

What is the best Arc browser alternative?

It depends on what you used Arc for. Dia is the easiest move because it imports Arc directly and comes from the same company; Zen is closest to Arc’s layout; Vivaldi lets you rebuild most of Arc yourself; Edge and Chrome are the safe defaults at work.

Is there an Arc alternative for Windows?

Yes. Zen, Vivaldi, Microsoft Edge and Chrome all run on Windows. Dia’s Windows version is new, so check Dia’s site for current support.

Is there an Arc alternative for Linux?

Zen and Vivaldi both run on Linux, and so does Chrome. Arc never had a Linux version, so Linux users moving from another machine usually pick Zen for the layout or Vivaldi for control.

Will my Arc extensions work in another browser?

Mostly. Dia, Vivaldi, Edge and Chrome are built on Chromium and install extensions from the Chrome Web Store, and Dia brings your Arc extensions over (TechCrunch). Zen is built on Firefox and uses Firefox add-ons instead.

How can a team keep its shared links when switching browsers?

Keep them outside the browser. Import your bookmarks HTML file into a shared Linkinize workspace and invite the team; everyone then finds the same links from the extension or the web app, whatever browser they use next.

Choose a browser for yourself, a home for your team’s links

Pick the Arc alternative that fits how you browse: Dia for the easiest move, Zen for the look, Vivaldi for control, Edge or Chrome for the safe choice. Then put the links your team shares somewhere that will still be there when the next browser goes away.

Give your team’s links a home that outlives any browser. Linkinize is free for up to 4 workspaces and 10 members.

How to Export Your Arc Bookmarks Before Arc Shuts Down on December 22

Arc is shutting down. The Browser Company announced on October 22, 2026 that Arc will stop working on Mac and Windows on December 22, 2026, and that accounts will be deactivated with personal data deleted within 30 days (TechCrunch). If your work lives in Arc’s sidebar, now is the time to export your Arc bookmarks, while the app still opens.

This guide covers three ways out, what each one keeps, and how to land your links somewhere that does not depend on a single browser again. It reflects Arc’s final release at the time of writing, November 2026.

The Arc shutdown timeline

  • October 22, 2026: no new Arc accounts. Existing users keep working, and the latest version adds a data export.
  • November 23, 2026: Arc Search on iOS and Android loses its AI features, sign-in and tab sync.
  • December 22, 2026: Arc stops working on macOS and Windows, and accounts are deactivated.
  • Within 30 days after that: personal data is deleted.

Do not leave this for the last week. Exports are quick, but checking that nothing went missing takes longer than you think, especially across several Spaces.

Before you export: two minutes of prep

Arc keeps a lot of links in places that exports treat differently. Do this first:

  1. Pin what you want to keep. Arc’s own export lists every sidebar tab, but the converters in Option 2 skip unpinned Today tabs.
  2. Open every Space and every profile once, so you know what should show up in the export.
  3. Save your Easels: open your Library, select Easels, then Export All Easels. Arc saves a ZIP with each Easel as a web page. Easels do not move to Dia.
  4. Note your Boosts. They cannot be exported and do not move to Dia, so copy any code you want to keep.
  5. Export passwords separately if Arc saved them. A bookmarks export never includes passwords.

Option 1: Arc’s built-in Export Data

The final Arc release has an export of its own, described in Arc’s help article How do I export my data from Arc?

  1. Update Arc to the latest version.
  2. On Mac, open Arc → Settings in the menu bar and select Advanced. On Windows, press Ctrl+, and find Export Spaces and tabs in the Advanced section.
  3. Select Export Data, choose where to save the file, and select Save.

Arc saves a file named Arc Data Export.md, with one section per Space listing your Favorites, pinned tabs, folders and other sidebar tabs as links. As Arc’s help article puts it, the export is a list of links rather than a bookmarks file, so other browsers cannot import it as bookmarks.

For a single folder, right-click it and choose Copy All Links; on Mac, hold Option while the menu is open to copy them as Markdown with titles.

That makes it a good safety net and a poor migration format. Keep the file even if you also use one of the options below.

Option 2: Keep your folders by converting the sidebar file

Arc stores everything you see in the sidebar in a single file called StorableSidebar.json. Free, open-source converters turn it into a standard bookmarks HTML file, with one folder per Space and your folders nested inside.

  1. Quit Arc so the file is not being written while you copy it.
  2. Find the file:
  • Mac: ~/Library/Application Support/Arc/StorableSidebar.json
  • Windows: a folder starting with TheBrowserCompany.Arc_ under %LOCALAPPDATA%\Packages, then LocalCache\Local\Arc
  1. Run a converter on a copy of it, for example arc-export (Python, MIT license) or the browser-based export-arc-bookmarks, which processes the file locally.
  2. You get a .html bookmarks file that any browser, and Linkinize, can import.

Both tools are community projects that were last updated in early 2025, so check the result against Arc before you delete anything. Pinned tabs and folders come across well; Favorites depend on the tool, and Today tabs are skipped.

Option 3: Move to Dia

If you are staying with The Browser Company, its AI browser Dia imports your Spaces, Favorites, pinned tabs and folders straight from Arc, so you do not need to export first (Arc Help Center). Passwords, extensions and history come along too, with Spaces becoming Profiles and folders becoming Pinned Tab Groups (TechCrunch). Easels and Boosts do not move over. It is the smoothest path if you want an Arc-like browser. Still choosing? We compare the best Arc alternatives for teams, from Dia to Zen and Vivaldi.

Keep a copy from Option 1 or 2 anyway. The lesson of this shutdown is that a browser’s sidebar is not a safe place for links your work depends on.

Bring your links into Linkinize

Whatever browser you pick next, you can stop tying your links to it. Linkinize is a bookmark manager for teams: shared workspaces, tags and instant search, synced to a browser extension. Your bookmarks live in workspaces in the cloud, so they show up wherever you sign in, and your team can share them.

  1. Create a workspace for each Arc Space you want to keep, for example “Product”, “Clients” and “Personal research”. See how multiple workspaces work.
  2. In the workspace, open Bookmarks, click the dropdown and choose Import Bookmarks.
  3. Upload the .html file from Option 2, or the bookmarks export from any other browser.
  4. Review the list, untick what you do not need, rename titles if you like, and confirm.

The importer reads bookmarks HTML files. If you only have the Markdown file from Option 1, open it in a Markdown editor and export it as HTML first; the importer picks up every link in it. The full walkthrough is in how to bulk import bookmarks into a Linkinize workspace.

After the import, add tags in place of the folder levels you lost, and your links sync to every device. If you ever leave, you can export your Linkinize bookmarks just as easily.

Your checklist before December 22

  • Arc updated to the final version
  • Every Space and profile opened and checked
  • Things worth keeping pinned
  • Built-in Export Data file (Arc Data Export.md) saved
  • Easels exported as a ZIP
  • Sidebar file converted to .html, with folders checked against Arc
  • Passwords exported separately
  • Links imported into their new home, and spot-checked

Frequently asked questions

Did Arc browser shut down?

Not yet. Arc keeps working until December 22, 2026. After that date you can no longer sign in to or use Arc on Mac or Windows, accounts are deactivated, and personal data is deleted within 30 days (Arc Help Center).

How do I export bookmarks from Arc to Chrome?

Convert Arc’s sidebar file into a bookmarks HTML file with one of the converters in Option 2, then in Chrome open Settings → Import bookmarks and settings, choose Bookmarks HTML File, and select it. Arc’s built-in Export Data gives you a list of links in a Markdown file, which Chrome cannot import as bookmarks.

Can I export bookmarks from Arc to Safari or Zen?

Yes, with the same bookmarks HTML file. In Safari choose File → Import From → Bookmarks HTML File; in Zen, which is built on Firefox, open the bookmarks library and import the HTML file. Check that every Space arrived, since some converters’ files import differently from browser to browser.

Does the Arc export include my passwords?

No. Neither Arc’s Export Data nor a bookmarks file contains passwords. Moving to Dia brings them along (TechCrunch); for any other browser, export them separately before December 22.

Can I import my Arc export into Linkinize?

Yes. Linkinize imports bookmarks HTML files, so the converted file from Option 2 works directly. If you only have Arc Data Export.md, convert it to HTML in a Markdown editor first.

Never lose your links to a browser again

Browsers come and go; Arc will not be the last one to shut down. Keep the links your work depends on in one place that outlives any of them.

Import your Arc bookmarks into Linkinize. It is free for up to 4 workspaces and 10 members, no credit card required.

How Teams Build Smart Research Libraries

Every day, your team discovers, evaluates, and bookmarks resources: design patterns you like, articles about your market, competitor information, technical solutions, case studies from successful companies. But does this knowledge compound, or does it disappear?

Individual bookmarks are useful in the moment. A shared, growing library of bookmarked research becomes your team’s biggest competitive advantage.

Here is how teams build smart research libraries that become more valuable with every bookmark saved.

Why Research Libraries Matter

When you treat bookmarks as a collection that belongs to a team rather than an individual, something shifts:

Knowledge Does Not Leave

When a teammate who bookmarked valuable research leaves the company, all those years of accumulated knowledge leaves with them — unless it is saved in a team library.

A shared research library means departing employees’ knowledge stays with the organization. New hires can instantly access what the team has learned.

Compound Learning

Each project adds to your library. A design decision from Project A becomes context for Project B. Market research from Q1 becomes foundation for Q2 strategy. The more you use your library, the more valuable it becomes.

Faster Decisions

When you can instantly find all past research on a topic, decisions are informed by your team’s full context. You avoid re-evaluating vendors you already decided against. You build on technical solutions you already evaluated.

Better Onboarding

New team members do not start from scratch. They can search “design patterns we use” or “competitors to watch” and instantly see what the team has collected and learned.

Four Phases of Building a Research Library

Phase 1: Foundation (Week 1)

Choose your initial bookmark system. Migrate existing bookmarks from individual tools. Establish basic organizational structure: what are your main research categories? Create your shared workspace and import what exists.

Phase 2: Early Adoption (Weeks 2-3)

Start bookmarking new resources into your shared library. Make it a habit: after you research something, bookmark it for the team. Establish simple tagging conventions. Track metrics: bookmarks saved per week, active contributors.

Phase 3: Momentum (Month 2 onwards)

Your library is growing. You start discovering bookmarks saved by teammates that are relevant to your current work. New team members use the library during onboarding. You notice you are re-researching less frequently because past research is findable.

Phase 4: Compound Value (6+ months)

Your library has become an asset. New projects leverage months of accumulated research. Onboarding is dramatically faster because knowledge is discoverable. Team members spontaneously discover relevant bookmarks from teammates they have never spoken to.

What Makes a Library “Smart”

Accessible to Everyone

Every team member can instantly access what the team knows. No request required. No waiting for someone to share a link. Search and discover.

Organized by Topic, Not People

Bookmarks are organized by what they are about (competitive intelligence, design patterns, technical solutions) not who saved them. This way, researching a topic shows everything the team has collected on it.

Rich with Context

Each bookmark carries enough metadata that someone encountering it for the first time understands why it matters. Tags, descriptions, notes, and context are part of every bookmark.

Searchable

You can find bookmarks by keyword, tag, topic, date, or contributor. Semantic search finds relevant bookmarks even if you do not remember the exact tag.

Growing and Maintained

Your library grows every week with new bookmarks. Old bookmarks are reviewed and pruned. Dead links are updated. Your library is a living asset, not an archive.

The Math of Library Compound Value

Assume your team has 10 people, and each person bookmarks an average of 5 resources per week:

  • Week 1: 50 bookmarks. Most are duplicates of what exists elsewhere.
  • Month 1: 200 bookmarks. You are finding 10-15% of new research from teammate bookmarks.
  • Month 3: 600 bookmarks. You are re-using 25-30% of research from the library.
  • Month 6: 1200 bookmarks. 40%+ of your research needs are already answered in your library.
  • Year 1: 2600 bookmarks. New team members onboard 70% faster. Duplicate research is nearly eliminated. Decision speed increases 30-40%.

This is not linear value. It is exponential. The library’s value compounds with each new bookmark and each team member that uses it.

Building a Research Library is a Team Sport

A research library only works if the team participates:

  • Everyone saves: Finding a useful resource? Bookmark it for the team. Takes 5 seconds.
  • Everyone searches: Need research on a topic? Search the library before starting from scratch.
  • Everyone contributes: Add tags and notes that help teammates understand why you saved something.
  • Everyone benefits: As the library grows, every team member makes better decisions faster.

When your team treats bookmarks as a shared asset, something magical happens: knowledge stops being scattered and starts compounding.

Start Building Your Team’s Research Library Today

The most successful teams are the ones that systematically capture and build on what they learn. Your team’s research library is the difference between repeating the same research over and over and learning faster with each project.

Start your team’s research library today. Get Linkinize free for your first 14 days. Build the smart research library that gives your team a competitive advantage.

Smart Bookmark Organization for Research Teams

Every organization has a bookmarking problem. Competitive intelligence lives in individual browser tabs. Design inspiration is scattered across team members’ Pocket accounts. Technical references sit in notebooks no one shares. And when employees leave, the bookmarks they’ve accumulated simply vanish with them.

The cost is real: teams waste an estimated 150+ hours per year re-discovering resources that someone in the organization already bookmarked. New hires spend their first month asking “does anyone have the link to…” instead of being productive. Strategic decisions get made without the full picture because research is scattered across individual silos.

Bookmark organization is not a nice-to-have — it is a competitive advantage. Here’s how teams can build systems that capture, organize, and make bookmarks discoverable across the entire team.

Three Pillars of Team Bookmark Organization

Pillar 1: Capture Without Friction

Bookmarking only works if it is faster than not bookmarking. If it takes more than a few seconds, people will not do it consistently.

Linkinize makes capture frictionless: one click from your browser, auto-tagging, optional notes. You save the bookmark and move on. The system handles organization in the background.

Pillar 2: Organize with Meaning

A bookmark without context is barely useful. Why was this article saved? What project was it for? What decision did it inform?

Team bookmark organization means every saved resource carries enough metadata that someone encountering it for the first time understands its relevance: descriptions, tags, notes, who saved it and when.

Tag consistently so teammates can filter and discover. Use descriptive names so search works. Add brief notes on why something matters.

Pillar 3: Discover Instantly

Organized bookmarks are only valuable if people can find them. Team discovery is what transforms a bookmark collection from a passive archive into an active intelligence system.

Effective discovery includes: full-text search across bookmark metadata, browsing curated collections by topic or project, AI-powered suggestions for relevant bookmarks, and cross-team visibility so you can learn what other teams are researching.

A Four-Phase Implementation Framework

Phase 1: Assess (Week 1)

How does your team currently bookmark? Where does research live? What are your biggest pain points around finding things? Start with one team that has high bookmark needs.

Phase 2: Pilot (Weeks 2-3)

Set up a shared workspace. Migrate existing bookmark collections. Establish basic tagging conventions. Measure baseline metrics: how long to find a resource? How many duplicate research requests happen per week?

Phase 3: Expand (Weeks 4-8)

Based on results, roll out to additional teams. Establish organization-wide tagging standards. Create cross-functional workspaces for shared topics. Begin tracking ROI: time saved, duplicate research eliminated.

Phase 4: Optimize (Ongoing)

With broad adoption, enable AI-powered discovery. Review and prune stale bookmarks. Measure KPIs: active contributors, bookmarks saved per week, search success rate, new hire productivity.

Measuring Bookmark Organization Impact

Team leaders need metrics to justify investment in bookmark systems:

  • Onboarding speed: How quickly do new team members become productive? Target: 3-5 days for resource familiarization (down from 3-4 weeks).
  • Duplicate research rate: How often do multiple people independently research the same topic? Target: 60% reduction.
  • Time to find: How long to locate a known bookmark? Target: under 30 seconds.
  • Knowledge retention: What percentage of departing employees’ research is preserved? Target: 90%+.
  • Active contribution: What percentage of team members actively save bookmarks? Target: 70%+ monthly active.

Real-World Scenarios

Product Research

Your product team spends three months researching competitors, market trends, and customer feedback. Dozens of articles, reports, and competitive analyses get bookmarked. With scattered bookmarks, assembling a comprehensive market overview takes days. With team organization, it takes 10 minutes of searching.

Security Incident Response

A vulnerability is disclosed. Your security team needs every article, advisory, and remediation playbook you’ve bookmarked on similar vulnerabilities. Without organization, this is frantic searching. With it, it is a 30-second query.

Customer Success

A customer asks about technical integration options. Your team needs documentation, past conversations, and similar implementation examples. Organized bookmarks mean any team member can provide an informed response without asking “who handled this account?”

Building Your Team’s Knowledge Advantage

Teams that systematically organize and leverage bookmarked research compound their advantage over time. Every bookmark saved, every tag added, every discovery made builds a richer knowledge library. Teams with instantly discoverable bookmarks make better decisions and move faster.

The question is not whether bookmark organization is valuable — it is whether your team will build this capability before your competitors do.

Learn how Linkinize helps teams organize and discover bookmarks. Start your free trial today.

Linkinize vs Pocket & Raindrop: The Team Bookmark Manager Difference

Your team bookmarks research every day — competitive intelligence, design inspiration, technical references, customer case studies. But where does it go? Chrome tabs that disappear on restart. Browser bookmarks buried in folders no one remembers. Pocket accounts that only sync to personal devices. And when you need that article you bookmarked three months ago? You cannot find it.

The real question is not whether you should bookmark things — teams that preserve research move faster and make better decisions. The question is: how should your team bookmark to maximize the value of what you collect?

Pocket and Raindrop are built for individuals. Linkinize is built for teams. Here’s what that difference means in practice.

What Pocket & Raindrop Do Well

Both Pocket and Raindrop are excellent bookmark managers for individual users:

  • Pocket: Save articles from anywhere, beautiful reading experience, great for personal curation
  • Raindrop: Organized collections, collaborative features in paid plans, powerful search

But the moment you ask “how does my whole team use this?” — the cracks appear.

Where Pocket & Raindrop Fall Short for Teams

Discovery is Hard

In Pocket and Raindrop, you see what you bookmarked. You do not naturally discover what teammates collect. If your teammate bookmarked a competitive analysis and you independently research the same competitor, you will never know.

Linkinize treats team discovery as a first-class feature. Every team member can see the shared library and search across what others have collected.

Context Disappears

Pocket and Raindrop let you add notes, but most people don’t. Months later, you see a bookmark but do not remember why you saved it.

Linkinize makes context the priority. Rich descriptions and tags are built into the saving flow.

Onboarding is Slow

New teammates cannot instantly access what the team has learned. With Linkinize, new team members join and immediately access everything the team has bookmarked.

Integration is Limited

Pocket and Raindrop are apps you open to manage bookmarks. Linkinize integrates into your workflow — save from your browser, search from your tools, get AI suggestions.

How Linkinize is Different

Everything in Linkinize assumes you are saving for a team. Shared workspaces are the default. Bookmark in one click. Auto-tagging handles organization. Semantic search finds what you need. The more your team uses it, the more valuable it becomes.

Which Tool Should You Choose?

Choose Linkinize if:

  • Your team does research together
  • You need to discover what teammates have collected
  • Context and knowledge matter
  • You want to onboard new members within days, not weeks
  • Your team’s collective research should compound in value over time

Stop Re-Researching What Your Team Already Knows

Pocket and Raindrop are great for individuals. Linkinize is built for teams who want their bookmarks to compound in value. Every resource saved helps teammates. Every bookmark makes future projects faster. Every team member gets smarter from collective knowledge.

Start your free Linkinize trial today and see what happens when your team’s research becomes instantly discoverable.

Access Your Bookmarks Instantly with Linkinize for Raycast

We’re excited to announce that Linkinize is now available as a Raycast extension — bringing your team’s bookmarks right to your fingertips without ever leaving your keyboard.

If you’re a Mac user who relies on Raycast for your daily workflow, you can now search, open, and manage your Linkinize bookmarks in the same place you launch apps, run scripts, and control your tools.

Why Raycast?

Raycast has become the go-to launcher for developers and power users on macOS. It’s fast, extensible, and designed around the idea that you should never have to leave your keyboard to get things done.

For teams already using Linkinize to organize and share bookmarks, having instant access through Raycast means one less browser tab to open, one less context switch in your day.

What You Can Do

Linkinize Raycast extension on the search bookmarks command

Search Bookmarks Instantly

Open Raycast, type your query, and find the bookmark you need in milliseconds. Linkinize syncs your workspace bookmarks locally, so search results appear instantly — no network delay, no waiting.

Each bookmark shows its name, description, and favicon, so you can quickly identify the right link. Hit Enter to open it in your browser, or use ⌘C to copy the URL to your clipboard.

You can also set up a global keyboard shortcut (⌘⌥L by default) to jump straight into bookmark search from anywhere on your Mac.

Switch Between Workspaces

If you work across multiple organizations or workspaces in Linkinize, the Switch Context command (⌘⌥O) lets you quickly change which workspace you’re searching. No need to open the browser or the Linkinize app — just pick your workspace and your bookmarks update automatically.

Automatic Background Sync

The extension syncs your bookmarks in the background every 30 minutes, so your local data is always up to date. You can also trigger a manual sync anytime if you’ve just added new bookmarks and want them available immediately.

Getting Started

Setting up takes less than a minute:

  1. Install Raycast if you haven’t already (it’s free).
  2. Search for “Linkinize” in the Raycast Store, or visit the extension page directly.
  3. Install the extension and enter your Linkinize email and password when prompted.
  4. That’s it — start searching with ⌘⌥L.

Smart Ranking

Bookmarks aren’t just listed alphabetically. The extension uses a relevance-based ranking system that prioritizes the links you actually use. The more you open a bookmark through Raycast, the higher it appears in your results — so your most important links are always at the top.

Built for Teams

This extension works with all Linkinize plans. Whether you’re on a personal account or part of an enterprise team with dozens of workspaces, your bookmarks are available the moment you open Raycast.

And because everything syncs from your Linkinize workspace, any bookmark added by a teammate shows up in your Raycast search automatically — no extra setup needed.

What’s Next

This is just the beginning for our Raycast integration. We’re exploring features like creating new bookmarks directly from Raycast, quick actions for tagging and organizing, and deeper workspace management — all without leaving your launcher.

Have ideas for what you’d like to see? We’d love to hear from you — reach out through our contact page or drop us a message in your Linkinize workspace.

Install the Linkinize Raycast extension →

Linkinize Web, Now Better on Mobile

We’ve been quietly improving the Linkinize web app, and it’s now in a much better place than it was even a few weeks ago.

If you’re not using the extension or you’re just on your phone, the web app is really where Linkinize shines. Quick access, no setup, just open and go.

One of the biggest upgrades is the mobile experience. Everything feels lighter, faster, and just easier to use. Navigation is smoother, layouts make more sense on smaller screens, and overall it doesn’t feel like a “desktop squeezed into mobile” anymore.

Search also got a proper upgrade. You can now go through your bookmarks quickly without friction. Open the web app, type what you’re looking for, and it’s there. No digging, no guessing.

This is one of those updates that doesn’t scream for attention, but you’ll feel it immediately once you start using it.

More improvements coming soon

Introducing SCIM 2.0 Provisioning: Automate User Management in Linkinize

Managing user access across your organization shouldn’t be a manual, error-prone process. That’s why we’re excited to announce SCIM 2.0 provisioning support for Linkinize Enterprise customers.

With SCIM (System for Cross-domain Identity Management), you can now automatically provision, update, and deprovision users directly from your identity provider. No more manual invites. No more forgotten access. No more security risks from delayed offboarding.

What is SCIM and Why Does It Matter?

SCIM 2.0 is an open standard protocol that enables automated user identity management between your Identity Provider (IdP) and applications like Linkinize. It’s the backbone of modern enterprise identity workflows.

The Problem SCIM Solves

Before SCIM, IT teams faced common challenges:

  • Manual user provisioning – Adding each employee to every app individually
  • Delayed offboarding – Former employees retaining access for days or weeks
  • Inconsistent user data – Names and roles out of sync across systems
  • Compliance risks – No audit trail of who has access to what

How SCIM Changes Everything

With SCIM enabled, your identity provider becomes the single source of truth:

Action in IdPResult in Linkinize
Add user to groupUser automatically provisioned with correct workspace access
Update user profileName and attributes sync automatically
Remove user from groupUser instantly deactivated, access revoked
Disable user accountImmediate offboarding across all workspaces

Supported Identity Providers

Linkinize SCIM 2.0 works with all major enterprise identity providers:

Fully Tested & Supported

  • Okta – Full user lifecycle management with incremental sync
  • Microsoft Entra ID (Azure AD) – Seamless integration with Microsoft 365 environments
  • Google Workspace – Native support for Google Cloud Identity customers

Also Compatible

  • OneLogin – Enterprise identity management
  • JumpCloud – Cloud directory platform
  • Ping Identity – Enterprise SSO and identity solutions
  • Any SCIM 2.0 compliant provider – Standard protocol support

Key Features of Linkinize SCIM Integration

Automatic User Provisioning

When employees join your organization and are added to the appropriate IdP group, they’re automatically provisioned in Linkinize:

  • User account created instantly
  • Added to designated workspaces
  • Ready to collaborate immediately
  • No invitation emails or manual setup required

Real-Time User Updates

Keep user information synchronized automatically:

  • Name changes reflect immediately
  • Department moves update workspace access
  • Role changes propagate across the system

Instant Offboarding

When an employee leaves or changes roles:

  • Access revoked within seconds of IdP change
  • User deactivated (not deleted) to preserve data integrity
  • Audit trail maintained for compliance
  • No lingering access risks

Workspace (Group) Sync

SCIM Groups map directly to Linkinize Workspaces:

  • Create workspaces from IdP groups
  • Manage membership centrally
  • Keep team structures aligned with your organization

How SCIM Provisioning Works

Step 1: Enable SCIM in Linkinize

Organization admins can enable SCIM from the Plugins settings:

  1. Navigate to Organization Settings > Plugins > SCIM
  2. Toggle SCIM provisioning On
  3. Generate a Bearer Token (shown once – save it securely)
  4. Copy your SCIM Base URL

Step 2: Configure Your Identity Provider

Use the credentials from Linkinize to configure your IdP:

SCIM Base URL:

https://app.linkinize.com/scim/v2

Authentication: Bearer Token

Supported Operations:

  • Users: Create, Read, Update, Deactivate
  • Groups: Create, Read, Update, Delete

Step 3: Assign Users and Groups

In your IdP:

  1. Assign users to the Linkinize application
  2. Configure group pushes for workspace sync
  3. Set up attribute mappings (email, name, external ID)

Step 4: Verify Provisioning

Once configured, test the integration:

  • Add a test user in your IdP
  • Verify they appear in Linkinize within seconds
  • Remove them and confirm deactivation

Security & Compliance Benefits

Zero-Trust Access Management

SCIM enables a zero-trust approach to access control:

  • Centralized identity governance – One place to manage all access
  • Immediate access revocation – No delay between IdP change and app access
  • Principle of least privilege – Users only get access to assigned workspaces

Compliance & Audit

Meet regulatory requirements with confidence:

  • SOC 2 Type II – SCIM integration supports compliance frameworks
  • GDPR – Automated data lifecycle management
  • ISO 27001 – Centralized access control documentation
  • Complete audit trail – Every provisioning action is logged

Data Protection

Your security is our priority:

  • Bearer tokens are hashed – Raw tokens never stored
  • TLS 1.3 encryption – All SCIM traffic encrypted in transit
  • Organization isolation – SCIM tokens scope strictly to one organization
  • No cross-tenant access – Complete data segregation

SCIM vs. Manual User Management

AspectManual ManagementSCIM Provisioning
Onboarding timeHours to daysSeconds
Offboarding timeHours to weeksInstant
Human error riskHighEliminated
IT admin overheadSignificantMinimal
Compliance auditManual documentationAutomatic logging
User data accuracyOften outdatedAlways current
ScalabilityLimitedUnlimited

Frequently Asked Questions

What happens to existing users when I enable SCIM?

Existing users created through registration or invitation remain unchanged. SCIM only manages users it provisions. You can gradually migrate to SCIM-managed users over time.

Can SCIM delete users permanently?

No. SCIM deactivates users rather than deleting them. This preserves data integrity, audit trails, and allows for easy reactivation if needed.

What if a user exists in both SCIM and was manually invited?

SCIM will not overwrite manually managed users. If you attempt to provision an existing user via SCIM, you’ll receive a conflict response. This prevents accidental overwrites.

Can I use SCIM alongside SAML SSO?

Yes! SCIM and SAML SSO complement each other perfectly:

  • SAML SSO handles authentication (who can log in)
  • SCIM handles provisioning (who has accounts and access)

Most enterprise customers use both together.

Which plan includes SCIM?

SCIM provisioning is available exclusively on the Enterprise plan. Contact us to learn more about Enterprise features.

How do I revoke SCIM access?

Organization admins can revoke the SCIM token at any time from the Plugins settings. This immediately disables all SCIM operations while preserving existing user data.

Getting Started with SCIM

For Existing Enterprise Customers

SCIM is available now in your Organization Settings:

  1. Go to Settings > Plugins > SCIM
  2. Enable SCIM provisioning
  3. Follow the setup guide for your IdP

For Teams Considering Enterprise

SCIM provisioning is one of many enterprise features designed for organizations that need:

  • Automated user lifecycle management
  • Advanced security and compliance
  • Centralized identity governance
  • Dedicated support and SLAs

Contact Sales to discuss your requirements or Start a Trial to explore Enterprise features.

What’s Next

We’re continuing to invest in enterprise-grade features to make Linkinize secure, scalable, and easy to manage at any team size. Coming soon:

  • SCIM audit logs – Detailed provisioning history in your dashboard
  • Custom attribute mapping – Map additional IdP attributes to Linkinize fields
  • Provisioning rules – Conditional logic for workspace assignments

Learn More

Have questions about SCIM provisioning? Contact our team – we’re here to help.

Introducing Linkinize AI

This one’s been a long time coming.

We’ve officially shipped the new Linkinize release with AI built in, and it’s already live in the browser extension stores. It’ll start rolling out to users very shortly.

This update isn’t about slapping “AI” on the product for the sake of it. It’s about removing friction from something we all do every day: saving links, finding them later, and actually getting value out of them.

Continue reading “Introducing Linkinize AI”

Unlocking Smarter Decisions with Linkinize Insights

Organizations today rely on a growing ecosystem of external tools and services. From developer platforms and cloud dashboards to collaboration suites and analytics portals, the average team juggles dozens of links every day. While these tools are essential, they also come with hidden costs: licensing fees, overlapping functionality, and the risk of underutilization.

With our new Insights plugin, Linkinize now gives organization admins the clarity they need to manage this complexity.

Continue reading “Unlocking Smarter Decisions with Linkinize Insights”