diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index a06a7c90..a2ef5aa0 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -49,7 +49,7 @@
 
 <!--
   How can a reviewer confirm this works? Include test commands, manual
-  steps, or both. For UI changes, include before/after screenshots.
+  steps, or both.
 -->
 
 -
@@ -91,7 +91,6 @@
 - [ ] My branch name describes the change (e.g. `docs/...`, `fix/...`) and contains no internal Paperclip ticket id or instance-derived details
 - [ ] I have run tests locally and they pass
 - [ ] I have added or updated tests where applicable
-- [ ] If this change affects the UI, I have included before/after screenshots
 - [ ] I have updated relevant documentation to reflect my changes
 - [ ] I have considered and documented any risks above
 - [ ] All Paperclip CI gates are green
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 3b6e6ef7..10849c75 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -36,7 +36,6 @@ These almost always get merged quickly when they're clean.
   → Share rough ideas / approach
 - Once there's rough agreement, build it
 - In your PR include:
-  - Before / After screenshots (or short video if UI/behavior change)
   - Clear description of what & why
   - Proof it works (manual testing notes)
   - All tests passing and CI green
@@ -180,8 +179,6 @@ Then have the rest of your normal PR message after the Thinking Path.
 
 This should include details about what you did, why you did it, why it matters & the benefits, how we can verify it works, and any risks.
 
-Please include screenshots if possible if you have a visible change. (use something like the [agent-browser skill](https://github.com/vercel-labs/agent-browser/blob/main/skills/agent-browser/SKILL.md) or similar to take screenshots). Ideally, you include before and after screenshots.
-
 Questions? Just ask in #dev — we're happy to help.
 
 Happy hacking!