Supported Formats
Complete list of file formats and features
Outcome
Decide whether your file is on the right path before troubleshooting upload, preview, detection, or export behaviour.
Your progress
Mark each step as you complete it. This is saved only in this browser.
0 / 3 steps complete
Before you start
Know the file type you are trying to use, such as PDF, DOCX, XLSX, CSV, plain text, or log text.
If possible, know whether the document has selectable text or is scanned, photographed, or handwritten.
Use a synthetic file when you are testing the workflow.
Visual frame
Review asset
Supported formats storyboard
Synthetic formats frame only. It explains routing by format and keeps scanned, photo, and handwritten boundaries explicit.
ChooseFormat route
BoundaryCheck limitations
OutputInspect final
Synthetic frame
Format chooser
Route to the guide that matches the input.
PDFPage review
SpreadsheetColumn review
Log fileSecret review
Choosing the format route makes the next step clearer.
Format routing frame
A first-pass routing frame for file and text workflows. It helps users pick the right playbook before troubleshooting.
FormatWhat kind of input is this?
Readable textCan the browser read the text layer?
Output checkOpen the result before sharing.
Guided steps
Follow the task, then check the result.
Name the format and source
Start by identifying the file type and how it was created. A digital PDF, exported DOCX, spreadsheet, copied text, scanned page, photo, and handwritten note follow different support paths.
Format decision list grouped by text, PDF, office document, spreadsheet, and scanned/photo input.
Success check: You can name both the format and whether the content is machine-readable.
Open the closest format guide
Use the dedicated guide for the format. PDF, Word, spreadsheet, and log workflows each have different review points and failure modes.
Format routes to PDF, Word, spreadsheets, logs, or scanned/photo support.
Success check: You are using the article that matches the file you actually have.
Verify the output, not just the upload
A file path is only successful when the reviewed output matches what you intend to share. Open the exported result and check the sensitive areas before sending it onward.
Upload, preview, review, export, and inspect as separate checkpoints.
Success check: The exported file or copied output no longer exposes the sensitive values you reviewed.
Branch questions
Can you select text in the document before uploading?
Does the exported output match what you reviewed?
Completion check
You know which format-specific guide applies.
You separated upload/preview problems from detection/export problems.
You inspected the final output before sharing.
Support boundary
Support can use by default
- File type category and rough size band.
- Workflow step name such as upload, preview, review, or export.
- Browser metadata and user-written description after consent.
- Intent ID
- Article slug
- App route
- Browser and viewport
Requires your consent
- User-written description
- Email address
- Explicit attachment
- Redacted sample
- Support bundle previewed to the user
Not collected by default
- Raw original document text
- Full local file paths
- Pasted private content
- Unmasked screenshots
- Replay capture
Safe support summary
Copy a scrubbed handoff.
Redactorr KB support summary Article: /knowledge-base/supported-formats Selected issue: A format listed as supported fails at upload, preview, review, or export. Playbook progress: 0/3 steps marked complete Safe context to include: - File type category and rough size band. - Workflow step name such as upload, preview, review, or export. - Browser metadata and user-written description after consent. - Intent ID - Article slug - App route - Browser and viewport Requires explicit consent: - User-written description - Email address - Explicit attachment - Redacted sample - Support bundle previewed to the user Do not include by default: - Raw original document text - Full local file paths - Pasted private content - Unmasked screenshots - Replay capture User note: - Describe the step and symptom without pasting raw document text, secrets, files, or restoration material.
Article details
Supported File Formats
Redactorr support should be read as a measured capability, not a roadmap promise. Use this article to choose the safest format path for the file you have today.
Launch-Safe Format Paths
Plain Text (.txt)
- Paste, upload, or drag-and-drop text-like content
- Detection runs locally in the browser
- Export reviewed output after checking the result
- Best path when you need predictable support for logs, notes, configuration, or code snippets
- Best for: Log files, configuration files, code snippets
Word Documents (.docx)
- Use for reports, contracts, letters, and meeting notes
- Review headings, tables, comments, and tracked changes before export
- Export only after checking the document preview
- Best for: Reports, contracts, meeting notes
Excel Spreadsheets (.xlsx)
- Use for customer lists, structured finance data, and tabular inventories
- Review each sheet and high-risk column before export
- Charts and formula-heavy sheets need extra human review
- Best for: Customer lists, financial data, inventory
Gated Or Partial Format Paths
PDF Files (.pdf)
- Text-based PDFs are the safest PDF path
- Always inspect the visual output before sharing
- Scanned PDFs, photographed pages, and image-heavy layouts need OCR, export, and leakage checks before broad support claims
- Best for: Invoices, forms, letters
CSV Files (.csv)
- Treat CSV as a text-like structured format when it is opened as plain text
- Check headers, delimiters, and exported rows before sharing
- Spreadsheet workflows may be safer when formulas, tabs, or formatting matter
JSON/YAML
- Treat structured text as a review workflow, not a schema-preserving guarantee
- Check keys, nested values, secrets, tokens, and copied examples before sharing
PowerPoint (.pptx)
- Do not treat slide decks as broadly supported until the current product UI confirms support
- If you need help, export text or notes and review those in a supported workflow
Images and photos (OCR)
- Printed document photos require OCR and image-quality gates
- Broad image/photo redaction support waits for export leakage proof
HTML/XML
- Treat HTML and XML as text-like review material only when you are comfortable checking the exported structure yourself
Feature Matrix
| Format | Best current path | Extra review needed |
|---|---|---|
| .txt | Text review and export | Long logs, code blocks, copied secrets |
| .docx | Document review and export | Tables, tracked changes, embedded objects |
| .xlsx | Sheet and column review | Formulas, charts, multiple tabs |
| Text-based PDF review | Scanned pages, images, complex layout | |
| .csv | Text-like structured review | Delimiters, headers, exported rows |
| .json/.yaml | Text-like structured review | Nested secrets, schema expectations |
| .pptx | Extract text first | Layout, speaker notes, images |
| .png/.jpg | Not a broad support claim | OCR and visual leakage gates |
Limitations
Large files
- Break large files into smaller review units when the browser slows down
- Close unrelated browser tabs before processing heavy documents
- Keep a local copy of the original file so you can restart cleanly if needed
PDF Limitations
- Text-based PDFs only (Beta)
- Scanned PDFs require OCR, visual redaction, export, and leakage gates before broad support claims
- Complex layouts may lose formatting
Excel Limitations
- Macros are removed
- Charts are preserved but not analysed
- Pivot tables converted to static ranges
Word Limitations
- Embedded objects (videos, audio) removed
- Complex tables may lose formatting
- Track changes preserved but not analysed
Tips for Best Results
For PDFs:
- Use text-based PDFs (not scanned images)
- If layout is critical, export to Word first
- Try "visual redaction" mode for simple forms
For Excel:
- Limit sheets to 50 columns for best performance
- Use column filters to target specific data
- Export formulas before redaction if needed
For Word:
- Accept track changes before upload
- Remove embedded media for faster processing
- Use "plain text" mode for simple documents
For Large Files:
- Break into smaller chunks if possible
- Close other browser tabs
- Use "aggressive" mode to reduce processing time
Request a Format
Need support for a specific format? Email us at [email protected] with:
- File format (.xyz)
- Use case description
- A synthetic or already-redacted sample if one is available
We prioritise formats based on user demand.
Still stuck?
Copy a safe article handoff.
Start support with the article, the issue, and safe context. Raw document text, files, restoration material, and unredacted screenshots stay out unless you explicitly choose otherwise.
Support can start here
- Article slug
- Selected issue
- Screen name
- Action name
Redactorr support case Source: Article playbook: supported-formats Route: /knowledge-base/supported-formats Selected issue: A format listed as supported fails at upload, preview, review, or export. Safe context: - File type category and rough size band. - Workflow step name such as upload, preview, review, or export. - Browser metadata and user-written description after consent. - Article slug - Selected issue - Screen name or article section - Action name - Browser and viewport Only include with explicit consent: - User-written description - Email address - Explicit attachment - Redacted sample - Support bundle previewed to the user Do not include by default: - Raw original document text - Full local file paths - Pasted private content - Unmasked screenshots - Replay capture - Hidden diagnostic uploads User note: - Describe what you tried and what happened. Do not paste raw document text, secrets, files, restoration material, or unredacted screenshots.
Support case builder
One case format, wherever you start.
This is the same support case shape used by diagnostics and article handoffs.
Safe to include
- File type category and rough size band.
- Workflow step name such as upload, preview, review, or export.
- Browser metadata and user-written description after consent.
- Article slug
- Selected issue
- Screen name or article section
Consent boundary
Private material belongs behind an explicit consent step, not in the initial case.
6 default exclusions
Before you copy0/4 ready