Contact sales Log in
How it works

SharePoint stores the document. BoldDocServer edits it.

BoldDocServer connects to SharePoint Server through WOPI, the documented protocol Office Online Server also used. SharePoint keeps the files, permissions and versions. BoldDocServer gives your users the editor.

Architecture: users’ browsers connect over HTTPS to BoldDocServer, a Windows container that talks to SharePoint Server through WOPI. All three sit inside your network.YOUR NETWORKbolddocserver.yourcompany.localProject planYour users’ browsersNothing to installBoldDocServerWindows containerDocument EditorSpreadsheet EditorPDF ViewerWOPI integrationASP.NET Core · HTTPSRuns on servers you manageSharePoint ServerProject plan.docxBudget 2027.xlsxPDFVendor agreement.pdfPermissions · VersionsSharePoint ServerYour document repositoryHTTPSWOPIover HTTPS
Step by step

What happens when someone opens a file

Seven steps between a click in SharePoint and a saved change. Your user sees two of them: the file opening and the file saving.

Sequence diagram of a WOPI session between the browser, SharePoint Server and BoldDocServer, in seven steps described in the list next to it.Your user’s browserAny modern browserSharePoint ServerWOPI hostBoldDocServerWOPI clientOpens Project plan.docx in the library1Host page and an access token for this file2Loads the BoldDocServer editor with the token3CheckFileInfo and GetFile, with the token4File properties, user permissions and content5Document opens for viewing or editing6PutFile: saves changes to the same file7SharePoint stores the new version
  1. The user opens a file. They select a Word, Excel or PDF file in a SharePoint library, the same way they always have.
  2. SharePoint prepares the session. It checks the user’s permissions and creates an access token for that user and that file.
  3. The editor loads. The browser loads BoldDocServer and passes it the token, so the user doesn’t sign in again.
  4. BoldDocServer asks for the file. It calls SharePoint’s WOPI endpoints, CheckFileInfo and GetFile, with the token.
  5. SharePoint answers. It returns the file’s properties, what this user is allowed to do with it, and the content.
  6. The user works in the browser. The file opens in the Document Editor, Spreadsheet Editor or PDF Viewer.
  7. Changes go back to SharePoint. BoldDocServer saves edits to the same file through WOPI (PutFile), and SharePoint stores the new version.
Who does what

SharePoint and BoldDocServer each keep their own job

Nothing about how SharePoint stores and protects documents changes. BoldDocServer only takes over the editing that Office Online Server used to do.

Responsibilities of SharePoint Server and BoldDocServer
ResponsibilitySharePoint ServerBoldDocServer
Stores the documentsYes, in your document librariesNo. It reads and writes the file through WOPI while it is open
Decides who can view or editYes, with SharePoint permissionsFollows what SharePoint allows for each user and file
Keeps version historyYes, according to library settingsNot involved
Shows the document in the browserNot involvedYes: Document Editor, Spreadsheet Editor and PDF Viewer
Saves changesStores the updated fileSends the changes back through WOPI
Runs onYour SharePoint farmA Windows container on servers you manage
WOPI in plain terms

Six terms worth knowing

You’ll meet these in the documentation and in SharePoint PowerShell.

WOPI
Web Application Open Platform Interface. A documented protocol that lets a document host such as SharePoint work with a separate, browser-based editor.
WOPI host
The system that stores the files and decides who can use them. Here, that is SharePoint Server.
WOPI client
The application that displays and edits the files. Here, that is BoldDocServer. Office Online Server played this role before.
Discovery
A file the WOPI client publishes so SharePoint knows which file types it handles and which actions, such as view and edit, it supports.
Access token
A token SharePoint issues for one user and one file, so the editor can act for that user without a second sign-in.
WOPI binding
The SharePoint setting that points file types at a WOPI client. You change it with SharePoint PowerShell when you switch editors.
Switching from Office Online Server

Point SharePoint at BoldDocServer

Because both use WOPI, switching is a change of binding, not a migration. Your libraries and documents stay where they are.

  1. Deploy and test. Run BoldDocServer and open your own documents through a test farm or site.
  2. Plan the change. Pick a maintenance window and keep a way back.
  3. Change the binding. Remove the Office Online Server binding and add one for BoldDocServer.
  4. Check it. Open a Word, Excel and PDF file from a library.
  • SharePoint Server 2016
  • SharePoint Server 2019
  • SharePoint Server Subscription Edition
SharePoint Management ShellTypical commands
# Remove the existing Office Online Server binding
Remove-SPWOPIBinding -All:$true

# Bind SharePoint to BoldDocServer
New-SPWOPIBinding -ServerName "bolddocserver.yourcompany.local"

# Use HTTPS for the internal zone
Set-SPWOPIZone -zone "internal-https"

For illustration. Follow the documentation for the exact steps for your farm.

Questions

Frequently asked questions

What is WOPI?

WOPI (Web Application Open Platform Interface) is a documented protocol that lets a document host, such as SharePoint Server, work with a separate browser-based editor, such as BoldDocServer. Office Online Server used the same protocol.

Do users sign in to BoldDocServer separately?

No. Users sign in to SharePoint as usual. SharePoint passes BoldDocServer an access token for the user and the file they opened.

Does BoldDocServer change SharePoint permissions?

No. SharePoint decides who can view or edit each file. BoldDocServer receives what each user is allowed to do and follows it.

Can we switch back to Office Online Server?

Yes, while your Office Online Server farm is still in place you can bind SharePoint back to it. Remember that Microsoft ends support for Office Online Server on December 31, 2026.

Try BoldDocServer free for 30 days

Keep SharePoint, give your users browser editing back, and be ready before Office Online Server support ends on December 31, 2026.