Fix Collabora Online Copy and Paste Between Local Apps

When copy and paste works in your desktop apps but fails between those apps and Collabora Online, the operating system clipboard is not necessarily broken. The failure may be limited to the browser tab, a blocked browser permission, an embedded Collabora frame that cannot access clipboard APIs, or the type of content being pasted. A useful fix should let you copy a short text sample from a local app into a Collabora document, copy it back out, and confirm whether formatting or images also survive.

Run the checks below in order. Begin with plain text and keyboard shortcuts, then check browser permissions and the way your organization embeds Collabora. This separates a workstation problem from an integration problem without changing server settings unnecessarily.

Does the clipboard work between other local apps?

First confirm that the source and destination applications can exchange clipboard data outside Collabora. Copy a short, non-sensitive sentence from a local text editor and paste it into another local application. Then reverse the direction. If this fails, troubleshoot the operating system, remote desktop session, virtual machine, or clipboard manager first. Collabora cannot read content that never reaches the device clipboard.

If you are using Remote Desktop, a virtual desktop, or a browser running on a remote machine, check whether clipboard sharing is enabled for that session. A successful copy between two apps inside the remote session does not always prove that text can cross between the remote session and your physical computer. Test both directions and note where the transfer stops.

Does the keyboard shortcut work when Collabora has focus?

Open a document, click inside the text or cell where you want to paste, and use the operating system’s normal shortcut: Ctrl+C and Ctrl+V on Windows or Linux, or Command+C and Command+V on macOS. For a simple test, copy plain text such as “clipboard check 123” from a local app. Avoid beginning with an image, a large table, or styled content.

Collabora Online runs in a browser, so the editor must receive the keystroke while its document area is active. If focus is in the browser address bar, a search box, or another page control, the shortcut acts on that control instead. Click once inside the document and try again. In Calc, confirm that the intended cell or formula bar has focus; in Writer, place the insertion point in the document body.

Also compare the toolbar or context-menu Paste command with the keyboard shortcut. Browser clipboard rules can prevent a web page from reading the system clipboard on demand. Collabora’s own project history documents cases where the Paste menu displayed a prompt to use the keyboard shortcut even though Ctrl+V worked. If the shortcut works and the menu command does not, record that difference; it points toward browser clipboard access rather than a failed system clipboard.

Is Collabora Online open over HTTPS?

For modern browser clipboard APIs, the page generally needs to be in a secure context. Check that the address bar shows your organization’s trusted HTTPS address and that the browser does not report a certificate warning. Mozilla’s Clipboard API documentation explains that access to read or write the system clipboard is restricted to secure contexts and may also require user activation or browser permission.

If your Collabora deployment is behind a reverse proxy, users may see HTTPS while the proxy-to-server connection uses another protocol. Do not change proxy or Collabora TLS settings based only on the browser symptom. Ask the administrator to verify the external URL, TLS termination, and forwarded scheme against the official deployment instructions. If the public page is already HTTPS and only one integration fails, continue to the frame and permission checks.

Did the browser block clipboard access for this site?

Check the browser’s site permissions for the exact origin where Collabora is displayed. In Chromium-based browsers, use the site information or settings controls beside the address bar, or search the browser’s settings for “clipboard.” If the site is set to Block, change it only for the trusted document site and only if your organization permits clipboard use. Reload the document after changing a permission and test again with plain text.

Some browser versions show a prompt only when a page requests access during a user action. Accept a prompt only when you recognize the site and intended paste operation. Firefox and Safari do not expose the same Chromium clipboard permission controls, and their prompts or behavior can differ. A missing clipboard toggle is not proof that the browser is defective; test the supported keyboard shortcut and consult the current browser’s own permission UI.

Collabora announced a newer direct clipboard-access path with Collabora Online 24.04. That can make some paste operations smoother where the browser supports the relevant API and the user grants access. It does not mean every deployment or browser will show the same prompt, nor does it guarantee that rich text, images, and spreadsheets paste identically. Check your deployed Collabora version and the official release notes before asking an administrator to upgrade.

Is Collabora embedded inside another application?

If Collabora opens inside a portal, learning platform, or file-sharing product, the host application may embed it in a cross-origin iframe. In Chromium browsers, iframe clipboard access depends on the browser’s Permissions Policy as well as the user’s browser permission. The embedding page may need to delegate clipboard-read and clipboard-write to the Collabora origin. A user cannot repair a missing iframe policy by repeatedly changing browser permissions.

Ask the administrator of the host integration to inspect the actual iframe and the response’s Permissions-Policy header. The iframe’s allow attribute should grant only the clipboard capabilities required to the trusted Collabora origin, and the parent response policy must permit that origin. Do not use a broad wildcard allowlist as a shortcut. Exact origins depend on your deployment, and an ancestor policy can still block access even when the iframe itself declares an allowance.

This diagnosis is especially relevant when Collabora works at its direct URL but fails only inside the host portal, or when users on the same portal have consistent problems in Chromium browsers. Provide the administrator with the browser name and version, host and Collabora origins, whether the issue affects copy, paste, or both, and any browser console message that mentions clipboard access or Permissions Policy. Remove document contents and account details before sharing screenshots or logs.

Does plain text work while formatting or images fail?

If a short text sample pastes correctly but rich text, a spreadsheet range, or an image does not, the basic clipboard path is working. The remaining problem may be data format compatibility or browser sanitization. Browsers and applications can exchange several clipboard formats, but they do not preserve every style, formula, object, or image representation the same way. The browser may also sanitize HTML as a security measure.

Use the simplest format that meets your need. For text, try Paste Special or paste without formatting if that option is available in your Collabora interface. For a table, test a small range and verify that rows and columns land in the intended cells. For images, first confirm whether the image is actually present on the system clipboard by pasting it into another local image-capable app. A missing image after pasting text is not evidence that all clipboard access is broken.

When should you test another browser or ask for an update?

After testing local apps, HTTPS, shortcuts, and site permissions, repeat the same plain-text test in another browser supported by your organization. Use the same device, account, document, and source text so the comparison is meaningful. If one browser works and another does not, report the exact browser versions and whether Collabora is embedded. If all browsers fail only inside one host application, focus on its integration policy. If failures began after an update, compare the Collabora, host application, and browser versions with the last known working setup.

Do not assume that clearing all browser data, disabling security features, or upgrading one component will fix every case. These steps can remove useful site state or introduce a separate compatibility change. Prefer a private window only as a short diagnostic test, and avoid disabling extensions that your organization requires. Collabora’s support forum has documented an integration-specific clipboard report involving a host iframe and Chromium browsers; the later discussion described a custom host-side remedy. Treat such reports as examples of why a site-specific diagnosis matters, not as proof that the same bug affects every installation.

What does a successful fix look like?

• Plain text copied from a local app appears at the intended cursor or cell in Collabora.
• Text copied from Collabora can be pasted back into a local app.
• The same test works after reloading the document and opening it in the normal workflow.
• Any remaining loss of formatting or images is limited to those formats and is understood as a compatibility issue.
• If embedded, the result is confirmed inside the actual portal, not only at Collabora’s direct URL.

If the basic text test still fails after these checks, send your administrator the test results, browser and Collabora versions, whether the document is embedded, and the exact error wording. That evidence helps distinguish a workstation clipboard problem, browser restriction, iframe policy issue, and version-specific defect. The browser clipboard API has security boundaries by design, so a correct outcome may require an approved integration change rather than a user-side toggle.

Sources: Collabora Online 24.04 release notes; Mozilla MDN Clipboard API security and browser behavior; Mozilla MDN Clipboard read documentation; Collabora Online FAQ; Collabora Online support forum: embedded Moodle clipboard report.