How well does Collabora Online edit PowerPoint decks?
Collabora Online supports PowerPoint's pptx format, but fidelity varies by deck feature. Simple text-and-image slides usually open and save with little trouble, while masters, animations, embedded media and fonts need a check against your own decks. Collabora Online is a browser-based office suite built on LibreOffice technology, and it reaches users through the WOPI protocol, which lets a host application such as Nextcloud open a document in the editor. The Collabora Online product page lists docx, xlsx and pptx among the Microsoft formats it handles, alongside OpenDocument, PDF, RTF, CSV and Visio files. That list confirms format support only, not how every slide will look after a round trip.
You need this check when a team wants to present and edit in the browser while colleagues keep working in PowerPoint on the desktop. The risk is not that a deck fails to open. The risk is that a board deck or customer presentation is saved back with shifted placeholders, altered transitions, substituted fonts or missing media, and nobody notices until the day it is presented. Two groups should run the check first: the people who own master templates, because layout drift spreads to every slide built on them, and the presenters who rely on animations or embedded video. Ask your Collabora Online provider or your own test team to confirm how the editor handles each feature in your decks before you announce browser editing to users.
Plan the check as a short, repeatable test rather than a one-time demo. Collect a sample of real decks that cover your templates, speaker notes, embedded media and the fonts your organization uses, then open, edit and save each one in Collabora Online and reopen it in PowerPoint. Record every difference in layout, animation, media playback and notes. Decide in advance which differences block go-live and which are acceptable, and keep original PPTX files in the system of record until the sample passes. The Collabora Online release notes are the place to check whether a fix you need has shipped in the version you plan to run.
Which PowerPoint features need the most testing
PowerPoint decks combine layout, motion, media, typography and speaker material in one file, and each area can change when a deck passes through Collabora Online and back. The cards below separate those areas so a test plan can assign each one its own sample slides, checks and owner. Treat every card as a question to answer with your own decks, not as a statement about how a given feature will render.
Slide masters and placeholders
Masters, layouts and placeholders define the look of every slide, so a small change in how a master is read can alter dozens of slides at once. Expect differences in inherited font sizes, placeholder positions, background fills and theme colors, especially in decks built from several templates merged over time. Test by opening a template-heavy deck, adding a new slide from each layout, and comparing the placeholder geometry and inherited styles against Microsoft PowerPoint. Check that edits to the master propagate the same way in both editors.
Animations and transitions
Entrance, exit and emphasis animations and slide transitions are stored as timing trees that editors interpret differently when effects are nested, triggered by clicks, or chained with delays. Differences tend to appear in build order, trigger timing and in transitions that PowerPoint offers but the editor does not reproduce. Build a test slide for each effect family you rely on, run it through a save and reopen cycle, and record which effects survive, which change and which disappear. Confirm the outcome in the presenter view you will actually use.
Embedded audio and video
Embedded media depends on codecs, container formats and how the file is packaged inside the deck, and a browser-based editor may handle playback and trimming differently from the desktop application. Check whether each clip plays in the editor, whether start and end points are preserved, and whether poster frames and autoplay settings survive a round trip. Use the exact media files from your production decks, since re-encoded samples hide the problems you need to find. Record the browser and operating system used for each playback test.
Fonts and text metrics
Font substitution is one of the most common causes of reflowed text, broken line breaks and shifted layouts after a deck changes editors. Confirm which fonts are installed on the Collabora Online server, which are embedded in the PPTX file, and which fall back to a substitute with different metrics. Compare line breaks and text box overflow on your most text-dense slides, and ask your operations team to confirm the font packages installed in your container or system image before the test starts.
Speaker notes and comments
Speaker notes live in a separate notes master and are often where sensitive or contractual wording ends up, so losing or moving them is a real risk. Check that notes text, formatting and the notes page layout survive editing and export, and that comments and their authors are preserved when the deck is reviewed by several people. Include a deck with long notes, bulleted notes and hidden slides in your corpus, and compare the notes pane in each editor after a full round trip.
Charts and SmartArt
Charts carry embedded workbook data, and SmartArt is a diagram layer generated from its own data model, so both can change shape or lose linked data when a deck is saved in another application. Test whether charts stay editable, whether their data and formatting survive, and whether SmartArt remains a diagram or is converted to shapes that no longer update. Open each chart and diagram type your organization uses, edit a value, and save. Ask the reader to confirm each result against the original file in Microsoft PowerPoint before accepting the deck as ready.
How PPTX files move between the WOPI host and the browser
A PowerPoint deck never opens in the browser on its own. The WOPI host, such as Nextcloud, stores the .pptx file and hands Collabora Online a WOPI request that points to it. Collabora Online fetches the file through the WOPI host, loads it into its LibreOffice-based engine, renders the slides in the browser, and saves edits back through the host in the format the user chooses. Each step is a point where a PPTX can be altered, so the request path belongs in your fidelity test plan. Confirm with your WOPI host which file types it sends to the editor, and confirm which save formats it accepts when a user edits a PPTX.
Collabora Online keeps the state of an open document in one server process, so every user who edits the same deck has to land on the same pod. The official Helm chart says horizontal pod autoscaling is disabled because scaling breaks collaborative editing and copy and paste, and that load balancers must route by the WOPISrc parameter. Your ingress, whether Nginx, HAProxy or the OpenShift Router, needs that routing rule before you open the service to users. Ask your platform team to test it with two browsers on one deck and confirm that a restart of one pod does not split an active session.
For presentations, this routing decides whether several people can work in one deck without conflicts. Test simultaneous edits to slide text, speaker notes and slide order, and check that a failover or rolling update does not drop unsaved changes. If your deployment runs multiple replicas, set the replica count by hand and document who changes it and when. Treat a deck that fails under concurrent editing as a go-live blocker for teams that co-edit presentations.
When to keep originals in PPTX and when editing in place is enough
Internal decks with plain text, standard layouts, basic images and few transitions are the easiest case for editing in place. Teams can open, revise and share them in the browser without a separate PowerPoint copy, and the main review effort is a visual check of slide text, images and tables after the first save. Routine status updates, meeting agendas and working drafts usually fall here.
- Editing in place: Suitable when the deck is a working document that is not shipped outside the organization.
- Layout check: Confirm that slide masters and placeholders still show the expected fonts, positions and colors after a save.
- Template reuse: If the deck is built from a corporate template, test one file from that template before the whole library moves.
- Sample set: Round-trip a handful of representative decks from your own shared drives, not only the simplest ones.
- Original retention: Keep the uploaded PPTX in storage so a reviewer can reopen the untouched version if a problem appears.
Before you rely on this path, ask Collabora Online operators to confirm which fonts are installed on the server, since missing fonts are a common cause of visible layout change.
Decks with complex animation sequences, embedded audio or video, or interactive elements carry more risk in any round trip. Editing these decks in Collabora Online is possible for many cases, but timing, triggers and media playback should be treated as items to verify rather than assumed to survive every save. The safer pattern for decks that are presented from a specific file is to keep a PowerPoint master and use the browser editor for light text changes only.
- Keep a master: Retain the PowerPoint file as the authoritative copy for presentation timing and media.
- Limit browser edits: Use the browser for text corrections and content updates that do not touch animation sequences.
- Test playback: Open the saved file in PowerPoint and run every animation trigger and media item.
- Media formats: Confirm which embedded audio and video formats play in your target environment and browsers.
- Review before release: Final presentation files should be checked in PowerPoint, not only in the browser.
Ask your Collabora Online implementer to test a deck with your actual animation and media content, because the result depends on the specific effects used.
Decks sent to customers, partners, regulators or the public are seen by people who will judge the output in PowerPoint, Keynote or Google Slides. Any drift in layout, fonts or notes that appears after a browser save is visible to those recipients, so the review standard should be higher than for internal work. The recommended handling is to edit in place where the change is small, then review and export the final version in PowerPoint before it leaves the organization.
- Final review: Open the release candidate in PowerPoint and check every slide, including notes and hidden slides.
- Font substitution: Confirm that recipients will see the intended fonts, or embed fonts where your policy permits.
- Speaker notes: Verify that notes survived the save and contain nothing that should not be shared externally.
- Version control: Keep the approved PPTX as the distributed artifact, with a clear version label.
- PDF copies: Where a fixed-layout copy is needed, export it from the approved PowerPoint file rather than the browser version.
Before a deck goes external, confirm who signs off on the final file and which version of the source is archived with it.
Board packs, regulatory submissions, clinical or safety briefings and other decks that serve as records need a defined original and a traceable history. Editing these files in Collabora Online can be appropriate, but the organization should decide in advance which version is the record and how changes are logged. Most teams keep the signed or approved PPTX as a preserved master, and treat browser edits as drafts that must be reconciled before approval.
- Designated record: Name one file as the record copy and store it in a retention system with access controls.
- Change history: Use document version history in your platform and record who approved each release.
- Draft separation: Keep working drafts in a separate location so they cannot be mistaken for the record.
- Format evidence: Retain the original upload alongside any saved version so the difference can be shown later.
- Policy alignment: Check the approach against your records management and data retention policies with your compliance team.
Ask your compliance and records owners to confirm which retention and approval rules apply before deciding whether browser editing is permitted for these decks.
Configuration choices that affect PPTX editing
This table compares the configuration decisions that change how PowerPoint decks behave in Collabora Online, from who can edit to which edition and deployment method you run. Read each row against your presentation workload, since the choice that suits a pilot can differ from the one that suits a production deck library. The main takeaway is that permissions, save format and edition should be settled before you test decks, so fidelity results reflect the setup you will run.
| Decision | Option and what it changes | When it fits |
|---|---|---|
| Edit versus view rights | Nextcloud Office can limit which groups may use the editor and which may edit rather than only view. Restricting edit rights keeps decks read-only for audiences that only present them. | Use view-only groups for board packs and published decks, and edit groups for teams that maintain masters and slides. |
| Save format for new decks | Saving as OOXML (PPTX) keeps files in the format your partners open in PowerPoint. Saving as OpenDocument (ODP) suits partners that require ODF, but PowerPoint round trips then need checking. | Choose PPTX when decks leave your organization. Choose ODP when internal policy or public sector rules require it. |
| Originals kept in PPTX | Keeping source files untouched and editing copies in Collabora Online limits risk from masters, animations and embedded media that may change on save. | Use for contractual, brand or regulated decks where the original file must stay the record. |
| CODE edition | Free and released roughly monthly as a rolling release. Collabora describes it as suited to testing, home use or small teams, not production. | Use for pilots, fidelity testing and proof of concept decks, not for live presentation libraries. |
| Business plan subscription | Priced at 3 euros per user per month for up to 99 users, per the pricing page. Includes long term support, an SLA, signed security updates and customer portal access. | Fits production deployments under 100 users that need supported patches for deck editing. |
| Enterprise plan subscription | Quoted for 100 or more users with volume discounts. Adds integration support, customization services and roadmap input. | Fits larger rollouts or teams that need custom master handling or integration work. |
| Docker deployment | Runs from collabora/code images on x86-64, ppc64 or arm64. Font packages and theme assets must be added to the image to match the fonts in your decks. | Fits pilots and smaller single-server setups where you control image contents. |
| Kubernetes deployment | Uses the official Helm chart, which keeps replicas fixed because scaling breaks collaborative editing. Users editing one deck must reach the same pod through WOPISrc-aware routing. | Fits large deployments with shared deck libraries and routing controls. Confirm pod resource limits against your concurrency. |
How to set up a PowerPoint compatibility test before rollout
This sequence turns a handful of representative decks into a documented, evidence-based decision on whether Collabora Online can open, edit and save PowerPoint files well enough for your organization. It ends with a list of blocking and non-blocking differences that your stakeholders have agreed to in writing.
Assemble a corpus of representative decks
Collect decks from real use across the teams that will edit presentations in the browser, such as sales, training, board reporting and marketing. Include the templates and masters your organization relies on, decks with embedded video and audio, decks with speaker notes, and decks built from fonts that are not installed by default. Remove sensitive content or replace it with sanitized copies, and record each file's owner, source application and version of PowerPoint that last saved it. Check: the corpus has a written inventory, every feature category in your scope has at least one deck, and the owners have confirmed the files are the ones they actually use.
Deploy a test Collabora Online instance
Your platform or infrastructure team deploys a non-production Collabora Online instance using the same method you plan to use in production, whether Docker images, system packages or Kubernetes. Match the production version and the fonts installed on the server as closely as you can, because font availability affects layout. Keep the test instance off any production document store. Check: the server reports the version you intended to test, and a sample presentation opens in the browser from the test host without errors.
Connect the test instance to a WOPI host
Connect the test Collabora Online server to a test WOPI host, such as a Nextcloud instance, using the same protocol and host naming you will use in production. Follow the Nextcloud administration guidance on restricting WOPI requests to the Collabora server addresses and using HTTPS for the server URL. Give the test group permission to edit, not only view, so that save behavior is tested. Check: a user can open, edit and save a test deck from the WOPI host, and the saved file appears in the host with the expected name and size.
Open, edit and save each deck
For each deck in the corpus, a tester opens the file in Collabora Online, makes a fixed set of edits (change a slide title, move a placeholder, edit speaker notes, apply a layout change, and play the slideshow), then saves it back to the WOPI host as PPTX. Run the same edits on the same deck each time so results can be compared. Keep the original file untouched and store the saved copy alongside it. Check: every deck has an original, an edited and saved copy, and a short record of which edits succeeded, failed or produced visible errors.
Compare results against PowerPoint
Open each original and saved copy in Microsoft PowerPoint, using the version your organization runs, and compare them side by side. Check masters and layouts, placeholder positions, fonts, transitions and animations, embedded media, tables, charts, images, and notes. Slideshow playback is one of the most visible behaviors, so run each deck in slideshow mode in both applications. Record each difference with the slide number, the feature, and a screenshot. Check: every deck has a completed comparison sheet, and each difference is tied to a feature category and a slide.
Log differences by feature
Group the logged differences into feature categories such as masters and placeholders, animations, embedded media, fonts, notes and tables. For each entry, record whether the problem appears on the original file, on the saved copy, or only after repeated saves, and whether a user can work around it. Assign a severity that your editorial, legal and communications owners agree on before testing starts. Check: the log is reviewed by at least one owner per feature category, and each entry has a status, an owner and a severity.
Decide go-live blockers and fallback rules
Hold a short review with the owners and decide which differences block rollout for each team, which are acceptable with a documented workaround, and which mean that a specific deck type should stay in PowerPoint. Write down the rule for keeping originals in PPTX, such as who keeps the master copy and when a deck must be opened only in desktop PowerPoint. Confirm any open questions with Collabora for the version you plan to run and with your own fonts and templates. Check: a signed or approved decision record lists blockers, accepted differences and fallback rules, and it names the people who will review it after rollout.
Security controls for presentation files in Collabora Online
Presentation files reach Collabora Online through the WOPI host, so the controls that protect them sit at the boundary between Nextcloud and the Collabora server. The four cards below cover network restriction, transport encryption, edit rights and patching, and each one should be checked in your own environment before decks with confidential content are opened.
Restrict WOPI requests by source IP
The Nextcloud administration manual recommends limiting WOPI requests to the IP addresses of the Collabora servers. For PowerPoint decks, this means only your Collabora nodes can fetch a presentation from Nextcloud and send it back, so a stray client or unrelated host cannot act as a WOPI caller. Confirm the addresses that reach Nextcloud after your load balancer and proxies, because a reverse proxy that rewrites the source address can make the allow list block legitimate traffic or allow more than you intended.
Use HTTPS on both sides
The Nextcloud manual advises using the same protocol for the Collabora server URL as for the Nextcloud installation, preferably HTTPS. Mixed schemes are a common cause of editing failures, and plain HTTP between the two services would expose deck contents, comments and speaker notes on the wire. Check that the URL configured in Nextcloud, the public address of the Collabora server and any internal hops all use HTTPS with valid certificates before you test a presentation.
Limit who can edit by group
In Nextcloud Office, administrators can restrict which groups can use the editor and which groups can edit rather than only view. For presentation files, this lets you keep read-only access for groups that only present or review decks, while editing rights go to the teams that maintain masters and templates. Review group membership for shared decks, because a change to master slides or embedded media affects every copy that is distributed from that file.
Patch from security advisories
Collabora publishes security advisories, and the 25.04 release notes record that 25.04.7.5, released January 29, 2026, fixed CVE-2026-23623 and that package signing keys were updated for RPM and DEB users. Subscribe to release notes for your branch, schedule point releases and verify package signatures during updates. Document which build is running in each environment so that you can show a document-handling vulnerability was closed on a given date.
Questions buyers ask about PowerPoint editing in Collabora Online
Is Collabora Online good enough for editing our PowerPoint decks?
It depends on which features your decks use, so the answer should come from testing your own decks rather than from general claims. Collabora Online supports the pptx format as part of its Microsoft format support, and it is built on LibreOffice technology. Simple text-driven slides with standard layouts usually behave differently from decks that rely on heavily customized masters, complex animations, embedded media or uncommon fonts. Ask for a short list of your decks, sorted by how much each one depends on those features, and test the most complex ones first. Where a deck fails, decide whether the gap is acceptable for editing or whether that deck should stay in PowerPoint.
What drives the testing effort for PowerPoint compatibility?
The main drivers are the number of decks, how varied they are, and how many people and workflows depend on them. Effort rises when decks use custom masters, many placeholders, animations, embedded audio or video, linked objects, or fonts that are not installed on the server. It also rises when decks are edited by several people in a round trip with PowerPoint on the desktop. Teams usually need to log each issue, record whether it affects content or only appearance, and agree which issues block go-live. Ask any provider to break the work into corpus building, test runs, issue triage and the final report, and to state which of these you own.
Who should run the PowerPoint compatibility tests?
The test should be run by people who know the decks and can judge whether a change matters, usually a small group from the business teams that own the presentations, supported by an engineer who can reproduce and log issues. Security or compliance staff should review any decks containing sensitive content before they are copied into a test environment. A partner can build the test harness, the corpus process and the issue log, but the acceptance decisions about which differences are acceptable belong to your organization. Ask for that split in writing before the work starts.
How long does a PowerPoint corpus test take?
The duration depends on the number of decks in scope, how complex they are, and how many rounds of retesting follow fixes or configuration changes. A small representative set can be tested in a short cycle, while a large estate with many templates takes longer, especially when a human must review each rendered slide. The exact duration must be confirmed in the written scope, where the deck count, test cases, review steps and acceptance criteria are listed. Ask for the timeline as a set of milestones tied to those items, not as a single figure.
Can our team run the PowerPoint compatibility test alone?
Yes, many teams can run a basic test themselves if they have someone comfortable with Collabora Online administration and a clear test method. Your team would need a working Collabora Online server, a WOPI host such as Nextcloud for opening the files, test accounts, a corpus of representative decks, and a way to record and compare results. The harder parts are building a corpus that reflects real usage, judging visual differences consistently, and deciding what blocks go-live. If your team has limited time or no one who can judge slide fidelity, a fixed-scope engagement can cover those parts while your staff keep ownership of the decisions.
What do we need to provide for the PowerPoint test?
Plan to provide sample decks that reflect real work, including the master templates your teams use, along with test accounts on the WOPI host, a running Collabora Online server, and the fonts and media your decks depend on. You should also name the people who will review results and approve or reject issues. Decks with confidential content need a decision on where and how they may be copied for testing. Confirm these inputs with the provider during scoping so that delays do not come from missing files or access.
What changes after a Collabora Online version upgrade?
Each upgrade can change how the editor renders or saves slides, so PowerPoint results should be retested after any move to a new branch. Collabora publishes release notes for each branch, and its security advisories can require point releases on older branches. Before upgrading, rerun the same corpus, compare rendering and saved output with the previous baseline, and check that the decks you keep in PPTX still open and save correctly. Ask your provider whether the test corpus and log are kept so each upgrade can be checked against the same baseline.
Limits to confirm in your own environment
Collabora Online renders PowerPoint decks through a LibreOffice-based engine, so fidelity depends on the exact version you run, the fonts and media codecs on your servers, and the templates your organization uses. The cards below list the items to test rather than assume, and each one should be checked against your own decks before go-live.
Fidelity per deck feature
Fidelity is not a single yes or no for PPTX. Masters, placeholders, transitions, animations, SmartArt, charts and grouped shapes can each render differently in the Collabora Online version you run. Build a short matrix that lists each feature your decks use, record the result in your pinned version, and repeat the test after every point release, because the 25.04 branch was still receiving point releases in 2026.
Font availability on servers
Editing happens on the server, so a deck that looks correct in Microsoft PowerPoint can reflow when a corporate or licensed font is missing on the Collabora host. Ask which fonts are installed in your container image or package, which ones your decks embed, and how substitutions are chosen. Check line breaks and text overflow in placeholders after opening, because those are the first symptoms of a substitution.
Embedded media playback
Audio and video embedded in slides depend on codecs and playback components available on the server and in the browser. Confirm which media types your decks contain, test playback in each browser your staff use, and check whether linked media (external files) resolves from the server at all. Treat media as a separate test, since a deck can open cleanly and still fail when a presenter presses play.
Behavior of custom templates
Corporate .potx templates and slide masters with custom layouts are the most common source of surprises. Test a deck built from each approved template, then edit the master, add a placeholder and save back to PPTX. Confirm that layouts, theme colors and placeholder inheritance survive the round trip in both directions, and record any layout that Microsoft PowerPoint shows differently.
Speaker notes and comments
Notes pages and reviewer comments are often lost or altered when a deck passes through a browser editor. Confirm that notes are visible, editable and saved back, that comment threads keep author and date, and that notes formatting such as bullets survives. If your review process depends on these, make them a blocking test before rollout.
AI assistant status in 26.04
Collabora Online 26.04 adds an optional AI assistant across Writer, Calc and Impress, and it is off by default. Confirm that it is disabled in your deployment, check which administrator setting controls it, and decide whether any provider is external or runs on your own infrastructure. Record the decision in your change record, because a deck sent to an external provider is a data flow your privacy and security reviewers need to approve.
What a DeployOpen PPTX compatibility engagement covers
A DeployOpen PPTX compatibility engagement produces a documented fidelity baseline for your own decks, run in your own infrastructure, so your team can decide which presentations open and edit acceptably in Collabora Online and which should stay as original PPTX files. The work starts with deck corpus design done together with your team. We help you select representative decks from the sources that matter to you, such as board packs, sales templates, training material and externally shared files, and we record why each deck was chosen. A corpus that only contains clean, simple slides will hide the problems that surface in production, so the selection criteria are agreed in writing before any test runs.
Test execution happens on a Collabora Online instance that you deploy and control, connected to your Nextcloud or other WOPI host. Engineers open each deck, check masters, layouts and placeholders, animations and transitions, embedded audio and video, fonts and speaker notes, then save and re-open the result in PowerPoint to compare. Each finding is logged with the deck, the slide, the expected behavior, the observed behavior, the Collabora Online version tested and a severity. Where a problem is caused by a missing font or a host configuration, we record that separately from a rendering defect, so the fix goes to the right owner. Confirm with us which Collabora Online branch and version your test environment will use, because findings are tied to that build.
The output is a fidelity log with blocker decisions, and a recommendation list for which deck categories remain in PPTX. Blocker decisions are proposed by the engagement team and confirmed by you, since only your business owners can accept a loss of animation or media behavior for a given use. The recommendations cover practical options such as keeping original files for externally distributed decks, setting a guidance note for users, or accepting edits in the browser for internal drafts. The scope, number of decks, test environments, deliverables and timelines are agreed in writing before work starts, and any extension, such as testing against additional Office versions or adding decks later, is priced through a change to that written scope.
How DeployOpen scopes and supports Collabora Online PPTX work
DeployOpen plans, implements and documents Collabora Online deployments inside your own infrastructure, including the PowerPoint test corpus, deck handling rules and operating runbooks that PPTX fidelity depends on. Engagements are fixed-scope, with scope and deliverables agreed in writing before work starts.
How we scope
- Written scope lists which PowerPoint deck types, templates and embedded media are in the test set.
- Scope states which decks must round-trip cleanly and which may be kept only in PPTX originals.
- Scope names the WOPI host, Collabora version and browsers that the fidelity results will cover.
How we build
- We assemble a representative deck corpus with your brand masters, animations, fonts and notes pages.
- We run round-trip tests in Collabora Online and Microsoft PowerPoint and log each difference found.
- We document which issues are fixed, accepted or blocking before go-live, with owners for each.
How we hand over
- You receive the test corpus, results log, and the decision record for each accepted limitation.
- You receive a written guide for users on when to edit in Collabora Online and when to keep PPTX originals.
- Runbooks cover font installation, deployment settings and the steps to repeat the test after upgrades.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after handover.
- Retainer work can re-run the deck corpus when Collabora Online branches or point releases change.
- Confirm with DeployOpen which support hours, response terms and upgrade coverage the retainer includes.
