
A LibreOffice Hybrid PDF includes an embedded editable ODF document. If you want to send only a review rendering of a client brief, inspect the Hybrid PDF option before export. The visible pages alone do not tell you whether editable source is also included.
Key Takeaways
- Hybrid PDF is intended to carry editable ODF alongside PDF pages.
- A normal review PDF and an editable-source handoff are different deliverables.
- Disabling hybrid output is not a substitute for removing sensitive content.
Identify the recipient's job
The LibreOffice PDF Export General documentation describes Hybrid PDF as embedding the ODF document for editing in LibreOffice. This can be useful when a collaborator must continue working on the brief.
It may be unnecessary when a photographer only needs the approved shot list. Ask which file the recipient needs to edit, and distinguish the source document from the review artifact in the delivery note.
Export the appropriate copy
Keep the editable master. Use the PDF export dialog and inspect the Hybrid PDF setting deliberately. For a review-only handoff, leave that option off and save the exported file under a distinct review name. For an authorized source handoff, label the file as hybrid so the recipient understands what it contains.
For a hypothetical client brief, the acceptance criteria might be: the supplier receives the ten approved pages, while the editable planning document remains in the internal project folder. Verify the selected export scope too; an accidental selection can omit pages even when the hybrid setting is correct.
Remove sensitive information at the source
A client name covered by a rectangle is still a different problem from an embedded ODF attachment. Use an appropriate applied-redaction workflow for the final PDF when actual removal is required. Do not describe an ordinary export as secure redaction.
Check comments, tracked edits, document properties and other retained material according to your organization's review process. Incremental PDF edits and metadata removal explain why changing one visible property does not establish that every prior value disappeared.
Keep accessibility separate from editability
Review-only does not mean inaccessible. The LibreOffice Accessibility Check documentation describes checks for document title, language, image alternatives and structure. Preserve those useful features when preparing the PDF.
Do not add restrictive settings merely to imply that source was removed. If you apply PDF permissions, review their interaction with assistive technology using the screen-reader permission guide.
As a proposed artifact check, close the source document and open a disposable copy of the exported PDF in LibreOffice. If the embedded brief opens for normal document editing, that reveals an editable source handoff; inspect it as well as the rendered pages. An unsuccessful open or edit does not prove there is no embedded source: reader behavior or an error may prevent this check. Keep that observation separate from a qualified inspection of the final artifact. Verify its visible scope and record the filename and actual export choice; normal display in a PDF viewer does not distinguish hybrid from ordinary output. For sensitive distribution, have the responsible reviewer inspect the artifact with suitable tools before sending it.
This guidance describes documented export behavior and an illustrative handoff. It does not certify a PDF as free of confidential information.
Related tasks
- Is a Black Rectangle Enough to Remove a Client Name from a Public PDF?
- Why Can Deleted PDF Metadata Still Be Recovered After an ExifTool Edit?
- Why Can a Client Open My Protected PDF but Not Read It Aloud?
Sources and scope
- PDF Export General: Embedded ODF content and confidential source disclosure risk.
Documentation-based guidance. Examples and acceptance checks are proposed, not measured software tests.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.