Initial document inspection
Preview supported publications to understand their page structure and visible content.
Select the option that fits your workflow.
Microsoft Publisher · Legal & eDiscovery
Make supported Publisher publications easier to inspect and route for review. Create working copies while retaining the original source documents and their collection context.
Inspect supported Publisher files and create working copies for review.
Preserve originals. Validate converted content before relying on it.
Supports eligible Microsoft Publisher files. Content completeness, image quality, and metadata retention vary by source and output. Compare working copies with the originals and record exceptions. Additional costs may apply.
Requires a supported Markzware application. Follow your organization’s collection, confidentiality, and handling procedures. Inspection and conversion do not replace forensic collection, legal review, or evidentiary validation.
For publications approved for public release, reuse selected text and available images as editable WordPress drafts. Follow your organization’s confidentiality and review requirements before publishing.
Archived .pub files may appear among business records and collected communications. Opening and understanding their visible content can be a practical processing step. Define the review objective first, retain the originals, and assess conversion output before relying on it in a wider document-review workflow.
Preview supported publications to understand their page structure and visible content.
Create supported outputs that your team can inspect without editing the original Publisher source.
Explore available text and structured document data for a planned downstream processing workflow.
Identify missing assets, unusual layouts, and files that require closer manual review.
Establish a reviewable working copy and an explicit exception list, without confusing format conversion with validation of legal or evidentiary requirements.
No. OmniMarkz provides publishing-document inspection and conversion capabilities. Collection, review-platform ingestion, legal holds, and evidentiary requirements belong to the broader workflow your organization defines.
Do not assume that it will. Keep the source and compare the metadata and content required by your review process before using converted output.
Potentially, through an appropriate integration. Confirm accepted formats, field mappings, content completeness, and validation requirements with the destination-system team.
Start with your files, your intended output, and the people who will review the result.
File support, output quality, and editability depend on the source document, available fonts and assets, and the chosen destination. Review a representative sample before expanding your workflow.