Confluence Companion App: Troubleshooting, Setup, and 2026 Alternatives

For over a decade, the Confluence Companion App served as the essential bridge between the web-based world of Confluence and the power of desktop applications like Microsoft Excel, Word, and Photoshop. It promised a simple life: click "Edit," change your file locally, and watch it save back to Confluence automatically.

However, in 2026, that bridge is looking increasingly unstable. Between the full removal of the app from Confluence Cloud and the phased "wind-down" of Confluence Data Center, many teams are finding that their "Edit" button has either vanished or simply stopped responding. Whether you are an admin trying to deploy a Microsoft Installer (.msi) package or a user desperately trying to recover edited files from a hidden cache, understanding the current state of the Atlassian Companion is the first step toward reclaiming your productivity.

This 2026 update provides the "ground truth" for the current ecosystem. We will explore how to keep the legacy bridge running if you are on a self-managed instance, why it disappeared for Cloud users, and how to enable file editing using modern, browser-native alternatives that require no local installation at all.

Is the Atlassian Companion App Still Supported? (Quick Status)

If you are currently searching for the Atlassian Companion App download link, your success depends entirely on which version of Confluence you are using. In 2026, the Atlassian landscape has a "hard line" drawn between Cloud and Data Center deployments.

The short answer is: Support is being phased out globally. While the app is technically functional for some, Atlassian has moved toward a "Cloud-First" strategy that leaves no room for local desktop bridges.

The "End of Life" Reality

For Confluence Data Center users, the latest version of the Companion App (v2.5.0) is effectively the final major release. As of March 30, 2026, Atlassian has ceased selling new Data Center licenses to new customers. While existing organizations can still use the app, no new features are being developed. The focus has shifted entirely to security patches and critical bug fixes to keep the bridge alive until the final site-wide shutdown in 2029.

Why Confluence Cloud Users Can't Find It

If you have migrated to Confluence Cloud, you may have noticed that the "Edit" button on your Confluence site has disappeared or changed. Atlassian removed Companion support for Cloud on March 31, 2022. The goal was to eliminate the "digital friction" of requiring every user to install and maintain local software. Today, if you want to edit a file on Cloud without downloading it, you must look toward modern Marketplace alternatives that run directly in your browser.

How it Works: The Protocol-Based Bridge

To understand why the Atlassian Companion app occasionally fails, you must first understand the "invisible handshake" it performs between your browser and your computer. Unlike a standard file download, Companion doesn't just hand you a file; it creates a persistent link between the Confluence page and your local environment.

The process relies on a custom URL scheme: the atlassian-companion: protocol. When you click "Edit," the browser sends a command using this protocol, which tells your operating system to wake up the Companion app running in the background.

The JWT Handshake

Security is managed through JSON Web Tokens (JWTs). Confluence issues a unique token to the Companion app on the user's machine, authorizing it to download the file and, more importantly, granting it the right to upload it back later. This ensures that every time a user edits a document, the connection is authenticated and secure without requiring the user to log in a second time inside the desktop app.

Breaking the "Download-Edit-Upload" Loop

This bridge is what allows Confluence to function as a central hub for specialized work. By using the app, you can open a file in your preferred desktop application, whether it’s a massive spreadsheet in Excel, a complex diagram in Visio, or a high-resolution file in Photoshop.

Once the file is open, the Companion app watches it. The moment you hit "Save" in your desktop software, the app detects the change and automatically begins the re-upload process. The file is saved as a new version in the Confluence history, effectively eliminating the manual friction of the traditional "download-edit-upload" workflow.

However, because this bridge relies on local protocols and background processes, any interruption in the "handshake", such as a browser security update or a restrictive firewall, can cause the entire system to stop recognizing the app.

Troubleshooting: "Companion App Not Recognized" (2026 Checklist)

One of the most common frustrations for teams is the "Endless Download Loop." You have the app installed, it’s running in your system tray, yet Confluence continues to prompt you to "Download the Atlassian Companion app" every time you click edit.

In 2026, this error is rarely about the installation itself and almost always about a broken "handshake" between your browser and the local protocol. Use this checklist to restore the connection.

1. The Protocol Handler Prompt

When you click "Edit," your browser should trigger a prompt asking for permission to open the atlassian-companion: link.

• The Fix: If you previously checked "Always allow" but it’s still not working, your browser’s registry might be corrupted. For Windows users, check HKEY_CLASSES_ROOT\atlassian-companion in the Registry Editor. If it's missing, a clean reinstall is required to re-register the protocol.

2. Restrictive Content Security Policy (CSP)

If your organization uses a highly secure domain configuration, your browser may refuse to launch the app due to a Content Security Policy (CSP) error.

• The Symptom: You click the button, and nothing happens, no prompt, no error on screen.
• The Fix: Check the browser console (F12). If you see a Refused to launch 'atlassian-companion:...' because it violates the following Content Security Policy directive, your admin needs to add the protocol and the trusted loopback domain to the allowed sources list.

3. SSO and the JWT "Silent Failure"

The Companion app uses JWT (JSON Web Tokens) to authenticate. If your Confluence site is behind a reverse proxy or a strict Single Sign-On (SSO) gateway (like Kerberos or F5), the token might be getting stripped or rejected.

• The Proxy Issue: Proxies often normalize URIs or block the /rest/token-auth/api/ path required for the handshake.
• The SSO Loop: If the app receives a login HTML page instead of a JWT token, it will fail silently. Ensure your reverse proxy is configured to allow the token-auth paths to pass through without re-encoding.

4. SSL Certificate & WebSocket Errors

To maintain security, Companion uses a specialized domain (atlassian-domain-for-localhost-connections-only.com) to establish a secure WebSocket connection to your computer.

• The 2026 Update: Modern browsers (especially the latest versions of Chrome and Firefox) have tightened security on "localhost" certificates. If your internal Root CA isn't correctly recognized, or if you've recently applied bug fixes that changed your network's proxy bypass rules, the WebSocket will fail, and the app won't be "recognized."

Administration: MSI Deployment and Virtual Environments

For IT administrators, managing the Atlassian Companion App across an entire organization requires a shift from individual user installs to a centralized deployment strategy. This is where the Microsoft Installer (.msi) package becomes the essential tool in your 2026 toolkit.

Deploying for Multiple Users with the MSI File

Unlike the standard .exe installer, which defaults to the user's local %LocalAppData% directory, the MSI file is designed for machine-wide installation. This ensures that the app is available to multiple users on a single workstation without requiring individual downloads.

• Installation Directory: By default, the MSI installs the app into the Program Files directory (usually C:\Program Files\Atlassian Companion).
• Silent Installation: To deploy the app silently via Group Policy (GPO) or Microsoft Endpoint Configuration Manager (MECM), use the following command: msiexec /i "Atlassian Companion.msi" ALLUSERS=1 /qn /norestart
• Custom Trusted Domains: You can pre-configure your Confluence site as a trusted domain during the install by passing a parameter: COMPANION_TRUSTED_DOMAINS="yourcompany.confluence.com"

The Terminal Server Challenge

A common 2026 hurdle is running the Companion App in terminal server environments (such as Windows Remote Desktop Services or Citrix). Because earlier versions of the app relied on a local WebSocket server bound to a specific port, multiple concurrent users on the same server would often clash, leading to the "File opened on another user's desktop" error.

The 2026 Reality for Virtual Desktops:

• Session-Based Desktops (RDS/RDSH): These are generally not compatible with the Companion App if users share the same network interface. The app struggles to distinguish between different user sessions attempting to use the atlassian-companion: protocol simultaneously.
• Virtual Desktop Infrastructure (VDI): If each user is assigned their own Virtual Machine (VM) with a unique network interface, the app is fully compatible.
• The "Confluence 7.3+" Exception: If you are on an updated version of Confluence Data Center, the app uses a browser-independent URI handler, which has significantly improved stability in Citrix environments. However, for seamless, multi-user file editing in the Cloud, virtual environments are one of the primary reasons organizations are switching to browser-native apps that don't require local background processes.

Disaster Recovery: Accessing the Atlassian Companion Folder

We have all been there: you spend three hours perfecting a complex spreadsheet or design file, hit "Save," and wait for the "Upload" notification, only for it never to arrive. Whether it's a network glitch or a closed browser tab, the "Edit" connection can sometimes break before your work is safely back in Confluence.

The good news? Your work isn't gone. When a user edits a file, the Atlassian Companion app saves a local copy to a hidden cache on your computer. If the automatic re-upload fails, you can manually recover edited files by navigating to these specific system paths.

Where to Find Your "Lost" Edits

The location of the Atlassian companion folder depends on your operating system and the version of the app you are running.

For Windows Users:

• Companion 1.1.0 and Later: %LocalAppData%\Atlassian Companion\Cache
• Companion 1.0.0: %AppData%\Roaming\Atlassian Companion\Cache
• Pro Tip: You can quickly search for the main folder by entering %UserProfile%\.atlassian-companion into the File Explorer address bar.

For macOS Users:

• All Versions: ~/Library/Application Support/Atlassian Companion/Cache
• Note: The folder is hidden by default on Mac. To see it, open your Home folder in Finder and press Command + Shift + . (dot) to toggle hidden files.

The 60-Day "Survival" Window

It is critical to act fast if you realize a file didn't upload correctly. By default, the Companion app performs a "cleanup" every time it restarts. Files modified more than 60 days ago are automatically cleared from the cache to prevent temporary files from filling up your hard drive.

If you find multiple subfolders with cryptic names, don't panic. Simply sort the folders by "Date Modified" to find your most recent work. Once you locate the file, we recommend copying it to your desktop and manually uploading it as a new version to the Confluence page to restore your single source of truth.

The Cloud Reality: Why the Companion App is Missing (and What’s Next)

If you are a Confluence Cloud user, you likely reached this guide because your "Edit" button vanished, or it now triggers a "Download" prompt that leads to a dead end. In 2022, Atlassian officially removed the Companion App from its Cloud roadmap.

The decision wasn't just about reducing "buggy" local experiences; it was a strategic move toward Forge-native architecture. Atlassian realized that requiring 100% of a company's staff to install a background utility just to edit a spreadsheet was a massive barrier to entry. Furthermore, with the 2026 rollout of Atlassian Guard's "Block Download" policies, a tool that relies on local downloading is fundamentally incompatible with modern enterprise security.

Community-Driven Stopgaps: Companion4Linux

For the highly technical users who felt left behind, specifically the Linux community, developers created Companion4Linux. This is an unofficial, open-source port of the Atlassian protocol designed to keep the bridge alive for the "Pinguin" OS. While it provides a way to recover edited files on Linux, it lacks official Atlassian support and can be broken by any major Cloud API update.

The 2026 Solution: ikuTeam’s Browser-Native Evolution

Instead of trying to fix a broken bridge, high-velocity teams have moved to the "Destination." ikuTeam’s Excel for Confluence, PDF for Confluence and Office for Confluence apps represent the modern standard for file editing.

By building directly on the Atlassian Forge platform, ikuTeam has brought the "Edit" experience inside the browser tab:

• No Local Install: Your IT team no longer needs to manage MSI files or troubleshoot local cache folders.
• Frictionless Collaboration: Unlike the Companion app, which "locked" files to a single user's machine, ikuTeam allows real-time co-editing. Multiple users can work on the same Excel sheet or Word doc simultaneously without version conflicts.
• Security & Compliance: Because the data stays within the Atlassian Cloud boundary and respects your site’s data residency settings, it bypasses the security risks of local file caching.

For Cloud users, the search for "alternatives" ends here. The goal is no longer to "connect" your desktop to Confluence, but to make Confluence powerful enough that you never need to leave it.

Verdict: Choosing Between the Legacy Bridge and Browser-Native Flow

As we navigate the workplace of 2026, the decision to stick with the Atlassian Companion App or move to a browser-native flow is no longer just about preference; it’s about the "End of Life" clock. With Confluence Data Center support officially ending on March 28, 2029, every organization must evaluate if maintaining a legacy bridge is worth the increasing productivity cost.

The Decision Matrix: Maintenance vs. Innovation

To help you decide, we have broken down the two paths based on the current 2026 standards for data management and security.

When to Stick with the Legacy Bridge (Data Center)

If your organization is currently tied to a Data Center instance and has a high volume of specialized files (like .PSD or .DWG) that require heavy-duty desktop software, the Companion App remains your only native option.

• The Checklist: Ensure your MSI deployment is up to date and your atlassian-companion protocol handlers are correctly configured across all browsers.
• The Warning: Be prepared for higher support volumes as browser security updates continue to break the local "handshake" protocol.

When to Move to the Browser-Native Flow (Cloud)

For any team on Confluence Cloud or Data Center teams looking to modernize, the browser-native flow is the clear winner. By using Excel for Confluence by ikuTeam, the PDF for Confluence or the ikuTeam Office for Confluence, you replace a "buggy" bridge with a permanent destination.

• Maximized Productivity: No more waiting for an app to wake up or dealing with "Save back to Confluence" failures.
• Superior Version History: Because edits happen in real-time, the version history is captured keystroke-by-keystroke, eliminating the risk of someone accidentally overwriting a "v2_Final" file with an older copy.
• Functionality: You get 100% of the spreadsheet functionality you need (formulas, pivots, and formatting) without the security risk of downloading sensitive data to a local hard drive.

Final Recommendation

The Atlassian Companion App was a brilliant solution for a "desktop-first" world. But in the era of Atlassian Rovo and real-time collaboration, the bridge is becoming a bottleneck. If you are on Cloud, embrace the browser-native future. If you are on Data Center, use this time to pilot ikuTeam as part of your 2029 migration strategy.