Redact HTML, Markdown, RTF, and rich text
Review rich text and markup while keeping an eye on links, comments, metadata, and rendered output.
Outcome
You can redact visible text and markup-adjacent values, then check the rendered or exported output before sharing.
Your progress
Mark each step as you complete it. This is saved only in this browser.
0 / 3 steps complete
Before you start
Visual frame
Review asset
Rich text format storyboard
Synthetic rich text frame only. It separates content review from formatting review and avoids broad claims across every rich-text source.
Synthetic frame
Rich text input
Know the source before judging the output.
Redact HTML, Markdown, RTF, and rich text workflow frame
Instructional frame for this operational guide. Replace with product screenshots only after the current screen state is approved.
Guided steps
Follow the task, then check the result.
Choose source or rendered review
Review the view that matches the risk. Source view helps with URLs and comments; rendered view helps with what a recipient will see.
Inspect links, comments, and attributes
Check URLs, alt text, comments, data attributes, headings, and inline examples for names, IDs, paths, or secrets.
Verify the shared form
Open the exported, copied, or rendered version and confirm it does not reveal values hidden from the main text view.
Branch questions
Can you see the rich-text or markup review surface described in this guide?
Did the result match the completion check?
Completion check
Support boundary
Support can use by default
- Article slug and selected workflow step.
- Screen or action name.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-redacted sample only after review.
- Intent ID
- Article slug
- App route
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/rich-text-format-redaction Selected issue: Rendered output and source output disagree after review. Playbook progress: 0/3 steps marked complete Safe context to include: - Article slug and selected workflow step. - Screen or action name. - Browser, viewport, workspace type, and file type category when relevant. - Synthetic sample shape or already-redacted sample only after review. - Intent ID - Article slug - App route 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
Redact HTML, Markdown, RTF, and rich text
Review rich text and markup while keeping an eye on links, comments, metadata, and rendered output.
Use this guide when the rich-text or markup review surface is available in your workspace. If you cannot see the screen or control described here, use the safe support path instead of guessing.
Outcome
You can redact visible text and markup-adjacent values, then check the rendered or exported output before sharing.
Before You Start
- Know whether you care about source markup, rendered output, or both.
- Use a copy of the content.
- Plan to inspect links and hidden-looking comments.
1. Choose source or rendered review
Review the view that matches the risk. Source view helps with URLs and comments; rendered view helps with what a recipient will see.
Check before you continue: You know which view you are using and why.
2. Inspect links, comments, and attributes
Check URLs, alt text, comments, data attributes, headings, and inline examples for names, IDs, paths, or secrets.
Check before you continue: Markup-adjacent sensitive values have been reviewed.
3. Verify the shared form
Open the exported, copied, or rendered version and confirm it does not reveal values hidden from the main text view.
Check before you continue: The shared form matches the reviewed state.
Completion Check
- Source and rendered risks were considered.
- Links, comments, alt text, and attributes were reviewed where relevant.
- The final shared form was opened or previewed.
Safe Examples
- A sample Markdown note with fake names.
- An HTML snippet using example.test links.
If You Need Support
Contact support when:
- Rendered output and source output disagree after review.
- Hidden comments or attributes are not visible enough to verify.
Include only support-safe context:
- Article slug and selected workflow step.
- Screen or action name.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-redacted sample only after review.
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.
- Article slug
- Selected issue
- Screen name
- Action name
Redactorr support case Source: Article playbook: rich-text-format-redaction Route: /knowledge-base/rich-text-format-redaction Selected issue: Rendered output and source output disagree after review. Safe context: - Article slug and selected workflow step. - Screen or action name. - Browser, viewport, workspace type, and file type category when relevant. - Synthetic sample shape or already-redacted sample only after review. - Article slug - Selected issue - Screen name or article section - Action name 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.
- Article slug and selected workflow step.
- Screen or action name.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-redacted sample only after review.
- Article slug
- Selected issue
Private material belongs behind an explicit consent step, not in the initial case.
6 default exclusions