diff --git a/rules/rubber-stamp-prs/rubber-stamp-pr-label.png b/rules/rubber-stamp-prs/rubber-stamp-pr-label.png
new file mode 100644
index 00000000000..568459d72a2
Binary files /dev/null and b/rules/rubber-stamp-prs/rubber-stamp-pr-label.png differ
diff --git a/rules/rubber-stamp-prs/rule.md b/rules/rubber-stamp-prs/rule.md
index 64bb79db034..233ec776597 100644
--- a/rules/rubber-stamp-prs/rule.md
+++ b/rules/rubber-stamp-prs/rule.md
@@ -18,7 +18,9 @@ Reviews are a crucial step in the PR process, as they ensure that the code/conte
 
 The rubber stamp label signifies that the change can be approved without extensive scrutiny. It is typically used for minor changes such as typos, formatting issues, or small documentation updates. By using a rubber stamp label, we can save time on reviews.
 
-![Figure: "Rubber stamp" label for GitHub Pull Requests](github-rubber-stamp-label.png)
+::: img-small
+![Figure: "Rubber stamp" label for GitHub Pull Requests](rubber-stamp-pr-label.png)
+:::
 
 To use a rubber stamp label effectively, you must follow some best practices: