ONLINE OFFICE VIEWER
View Office files online
Give users a practical way to open Word, Excel, and PowerPoint files without leaving your product.
office document viewer
Office SDK. Built to connect.
Collaborative web editors for AI agents, workflows, web apps and existing systems.
Self-hosted on your infrastructure.
Document outlineOutlineText formattingFormattingLists & checklistsChecklistsCommentsComments
Document outlineOutlineText formattingFormattingImages & tablesImages & tablesCommentsComments
Slide navigationSlidesImages & shapesImages & shapesText & typographyTypographyObject formattingFormatting
Office in your product. Docs on your servers.
Collaborative editors. Open APIs. Self-hosted.
PRODUCT STORY / FOUR EDITORSOne launch.
One launch.
Four editors.
See how one illustrative launch moves from research to proposal, operating numbers, and an executive decision without leaving the document workflow.
Open the full product story01
NOTES + MARKDOWNTurn research into a shared working context.02
WORD DOCUMENTTurn an approved direction into a formal proposal.03
EXCEL WORKBOOKTurn a plan into numbers people can operate.04
POWERPOINT REVIEWTurn operating detail into a decision-ready review. Privacy-redacted product screenshots with the imported templates openNorthstar data is illustrative.
THE WORKING DEFINITION
Office SDK is an embedded web document surface for products that need Word, Excel, and PowerPoint work to stay beside the surrounding record, permissions, and business process.
3 families:
Core Office families
Start with Word, Excel, and PowerPoint files that users already bring to the workflow.
3 modes:
Common user actions
Preview, edit, and review are separate experiences with separate acceptance checks.
4 stages:
Integration handoff
Context, surface, callback, and result make ownership visible from open to save.
COMPARE THE WORKFLOW
Choose the surface by the next action.
| Next action | Document surface | Host product keeps |
|---|---|---|
| Inspect a file | Preview | Identity, permission, and record context |
| Change content | Edit | Version owner and save destination |
| Move work forward | Review or import/export | Decision state and business result |
START HERE
Four checks before a build.
- Name the user action and the business record around the file.
- Map storage, permission, identity, and version ownership.
- Run representative files through the browser and backend path.
- Record the returned result and the owner of the next step.
01 / START WITH THE JOBSearch for the task.
Search for the task.
Find the product path.
Office is a large category. Meet people at the problem they already describe, then give qualified teams a reason to evaluate the right document workflow.
DOCUMENT EDITOR
Edit Word, Excel, and PowerPoint files
Put an editable Office surface next to the records, permissions, and workflows your app already owns.
online office editor
FILE WORKFLOW
Connect the file to the next step
Use callbacks to supply file information and permissions, then follow the documented result path back into your system.
office document callback api
REVIEW WORKFLOW
Review documents with context
Keep approvals and business records close to the document they explain.
document review and approval
02 / WHY OFFICE SDK
Make the file part of the product.
When the document is where the work happens, your users should not have to leave the system that owns the workflow.
Preview + collaborate
Embed a full Office document surface
Bring Word, Excel, and PowerPoint preview and collaborative editing into your web product. Users stay in the workflow that owns the file.
Import + export
Move files in and out cleanly
Use import and export flows to connect existing Office files with the document workflow your product provides.
Content operations
Work with document content
Read and write document and spreadsheet content, and keep comments and version history close to the business record.
Clear responsibility
Keep ownership boundaries explicit
Your system owns users, files, permissions, and business data. As an integration boundary, business-level records remain in your system while Office SDK provides the editor, rendering, format processing, collaboration, and JavaScript SDK surface.
Callback integration
Connect through your backend
Callbacks let your backend supply user, file, permission, and organization information to the embedded document workflow.
03 / OFFICE FILE FORMATS
Start with the files your users already have.
Use the format families below to frame the first conversation. Preview and editing support differ by format, so validate the exact behavior with your target files before committing to a production workflow.
Word documentsPreview: DOC, DOCX, DOT, DOCM, DOTX, DOTM, WPS, WPT · Import, edit, and export: verify the operation-specific path
Excel workbooksPreview: XLS, XLSX, CSV, XLSM, XLT, XLTX, XLTM, ET, ETT · Import, edit, and export: verify the operation-specific path
PowerPoint decksPreview: PPT, PPTX, POT, POTX, POTM, DPS, DPT, PPTM · Import, edit, and export: verify the operation-specific path
Broader preview coveragePreview: PDF, OFD, images, video, audio, text, and Markdown
Preview and editing coverage are stated separately so the product boundary stays clear.
04 / WHERE IT FITSUseful wherever
Useful wherever
documents move.
Use the first website to test high-intent Office workflows. The strongest ones become product pages, tools, and qualified conversations.
Content platforms
Preview and edit files where teams store and share them.
Review and approval
Connect a document to the people, notes, and decisions around it.
Education and research
Make reports, course packs, and spreadsheets useful in one place.
Operations and finance
Keep statements, plans, and business documents close to the system of record.
05 / DEPLOYMENT FIT
Plan the rollout with a known baseline.
Office SDK is designed to sit inside the web product that already owns users, files, permissions, and business data. Use the deployment baseline to frame the first technical conversation.
Talk through your environmentA web-based integration keeps the document workflow available across the environments your users already use.
Start with a focused validation environment, then move to a multi-node deployment when scale and availability require it.
The current deployment guidance gives platform teams a concrete baseline for planning an installation.
06 / NEXT STEP
Start with a clear product question.
The first version of this site is an orientation layer. It helps the right visitor recognize a use case, see the Office surface, and choose the next proof point.
Integration docsQuickstart, callbacks, and deployment reading for the build team.See the editors runFollow one workflow across the notes, Word, Excel, and PowerPoint surfaces.Office SDK on GitHubExplore Office SDK projects and repositories.Office format fitFrame the preview and editing boundaries that matter to your users.Evaluation conversationBring your workflow, data boundary, and deployment questions to the next discussion.
07 / QUESTIONS, ANSWERED
Make the next decision easier.
Short, honest answers for teams deciding whether an Office workflow belongs inside their product.
What is Office SDK?
Office SDK is an online document preview and editing service for teams that want to put Word, Excel, and PowerPoint workflows inside their own web product.
Which Office files should we evaluate first?
Start with the files your users already bring into the workflow. Evaluate preview, import, editing, and export paths separately for Word, Excel, and PowerPoint, with broader preview coverage including PDF and other common file types. Confirm the exact operation before launch.
Can Office SDK sit inside an existing product?
That is the intended evaluation path. Your system keeps file storage and permission decisions, while Office SDK provides the document surface, callback communication, and JavaScript SDK integration points.
How should we start evaluating Office SDK?
Start with one workflow and the file formats your users need. Identify the user action, target files, and deployment requirements, then validate the fit in a focused proof of concept.
Does Office SDK support PDF files?
PDF is supported for preview. Word, Excel, and PowerPoint are the editable Office file families; validate the exact behavior with the files and actions your workflow requires.
Who stores the files?
Your system does. Office SDK does not provide file storage. It communicates with your file system through documented callbacks and integration paths; apply your own storage, versioning, and permission rules to the resulting file or content.
Office SDK.
Built to connect.
Collaborative web editors for AI agents, workflows, web apps and existing systems.
Self-hosted on your infrastructure.