Practical guide · files stay on your device
Remove supported Office document properties locally.
Supported DOCX, XLSX and PPTX files can store properties such as author, last modified by and company. PixelRinse removes supported core, application and custom document properties locally; it is not a document sanitizer. Legacy DOC/XLS/PPT and OpenDocument files are not this cleaning workflow.
Publisher and editorial responsibility: Project Hubbs · Updated
Inspect your files for freeNo account required. Prepare resources explicitly before local processing. Inspection is free; cleaning and cleaned downloads require a license.
Can PixelRinse clean my file?
Real eligibility requires local inspection of the file and selected operation.
Key takeaways
- Inspect first for free. File format and structure—not the extension alone—determine eligible cleaning.
- Supported core, application and custom properties, such as author, last modified by and company.
- Properties cleaning does not remove comments, revisions or tracked changes, or embedded media.
Example
Synthetic walkthrough, not a customer file or recorded Office-reader test: quote.docx lists fictional author Mira Test and company Fjord Studio Ltd, and contains a comment from Mira. Property cleaning targets the supported properties; the comment and its author remain. Removing properties does not remove Mira’s name from a comment or visible text.
- Before · illustrative synthetic scenario
- Fictional author/company properties plus a comment from the author.
- After · intended supported scope, not a measured output
- Supported properties removed; the comment, review author and body remain. Confirm the properties report and reopen in Office.
How to do it safely
- Choose a supported Office file within the size limit, then explicitly Prepare and inspect if needed. Inspection is free.
- Review the properties found and the proposed changes.
- With Individual Pro, explicitly clean the file, then read the removed, retained and not-checked lists.
- Open the output in its Office application and review the body, comments and tracked changes yourself.
What this workflow removes
- Supported core, application and custom properties, such as author, last modified by and company.
What it does not promise
- Properties cleaning does not remove comments, revisions or tracked changes, or embedded media.
- Names typed in the body, headers, footers or file names remain.
- The 25 MiB file limit applies. Encrypted, signed, macro-enabled, malformed and unsupported packages are refused. Check the file-support page for exact formats.
Retained
- Body content, headings, cells, slides, headers and footers.
- Comments, review authors, revisions, tracked changes and embedded-media metadata.
Not checked
- Every possible identifying field in unsupported parts or embedded objects.
- Visual/layout equivalence in every Office reader. Open the downloaded copy in your normal application and review it.
Understand the evidence
Reparsed properties give bounded evidence for the supported scope. Areas outside it are listed as Not checked, never as passed.
Processing, comparisons and verification receipts stay local. PixelRinse sends no product-usage events. Payment and legacy license upgrades are separate online actions that never include selected file contents, names, hashes or metadata.
Common questions
- Are comments removed?
- No. Review and remove comments and revisions in your Office application first.
- Is the result a full sanitization?
- No. Only supported properties are covered.
More answers
What does PixelRinse do, and what does it promise?
PixelRinse provides private local tools for images, PDFs and metadata, plus supported comparisons and bounded document/media workflows.
Technical details and limits
Choose a working tool and inspect its exact support before processing. Metadata cleaning removes only the supported set; image editors intentionally change pixels. Each result states its checks and limits. No operation promises a file is free of every identifying trace.
Does PixelRinse blur faces or redact visible text?
There is no dedicated face-blurring or document-redaction tool. Metadata cleaning does not remove visible content.
Technical details and limits
Faces, text, license plates and reflections remain in a metadata-cleaned copy. Pixel editors such as background removal, retouching and text watermarks deliberately change images, but do not guarantee anonymization or complete redaction. Use an appropriate redaction workflow and review the final saved file.
What does Verified mean?
Verified means the bounded checks listed in the receipt passed on the rebuilt output.
Technical details and limits
Examples are that it parses, that supported metadata fields are gone and that retained content is intact. It describes those checks only, not every possible hidden trace.
Free inspection. One-time cleaning unlock.
Individual Pro is EUR 99 total, one-time, including applicable tax. No product tax is added on top. Lifetime (perpetual) use of the version you buy, plus 12 months of updates; update expiry does not revoke that access.
Merchant processing fees are covered. External network or issuer fees outside PixelRinse may be additional. Load purchase options on the pricing page to see currently configured methods.
Review pricing and payment options