Corrections policy
Everything on this site was written by people, and people get things wrong. What matters is how quickly an error is fixed and how honestly the fix is disclosed.
1. How to report an error
Use the contact form and include:
- The address of the page.
- The sentence or step that is wrong.
- What actually happens, and on which OBS Studio version and operating system.
- Anything that helps us reproduce it — a log file excerpt is ideal.
You do not need an account to report a correction, and reports are read by a person rather than sorted into a black hole.
2. How reports are triaged
| Severity | Examples | Response |
|---|---|---|
| Harmful | A step that can lose recordings, break a working configuration, or expose a stream key. | Page corrected or temporarily withdrawn as soon as the report is verified, ahead of other work. |
| Substantive | Wrong setting, obsolete instruction, incorrect claim about how OBS Studio behaves. | Verified and corrected, with a dated note on the page when the meaning changed. |
| Minor | Typo, broken link, unclear phrasing, stale screenshot. | Fixed in the normal editing cycle without a correction note. |
3. What a correction looks like
When a change alters the meaning of a page — a different recommendation, a removed step, a reversed conclusion — the page carries a short, dated note describing what changed and why. We do not delete the record of having been wrong. Minor copy edits are made without a note, because a changelog of typos helps nobody.
4. Withdrawal
If a page cannot be made accurate — the software changed fundamentally, the plugin is abandoned, the platform withdrew the feature — the page is retired. Where a better page covers the same ground, the old address redirects to it so existing links and bookmarks keep working.
5. What we will not do
- Remove accurate criticism of a product because a vendor asks.
- Rewrite history to hide an error that mattered.
- Publish a "correction" that is really a paid change of recommendation.
6. Complaints
If you reported something and disagree with the outcome, reply on the same thread and ask for it to be escalated. Legal complaints about copyright are handled separately under the copyright and takedown policy; naming and trademark questions are covered by the trademark notice.
7. Standing commitment
Every guide on this site is written and reviewed in house, tested against a named OBS Studio version, and updated when the software changes. When a walkthrough depends on a specific release, the version is stated in the guide.
This policy was last updated 6 August 2026.