diff --git a/img/fork_upstream_is_not_origin_parent.jpeg b/img/fork_upstream_is_not_origin_parent.jpeg
new file mode 100644
index 00000000..59910ddf
Binary files /dev/null and b/img/fork_upstream_is_not_origin_parent.jpeg differ
diff --git a/img/fork_upstream_is_not_origin_parent.png b/img/fork_upstream_is_not_origin_parent.png
deleted file mode 100644
index bfe2ee07..00000000
Binary files a/img/fork_upstream_is_not_origin_parent.png and /dev/null differ
diff --git a/remote-setups-common.Rmd b/remote-setups-common.Rmd
index 3d2d550d..6b33b6e3 100644
--- a/remote-setups-common.Rmd
+++ b/remote-setups-common.Rmd
@@ -204,7 +204,7 @@ Here is one last fork setup that's sub-optimal, but it can be salvaged.
 ```{r fork-no-upstream}
 #| echo = FALSE, fig.align = "center", out.width = "60%",
 #| fig.alt = "Setup described as \"fork_upstream_is_not_origin_parent\""
-knitr::include_graphics("img/fork_upstream_is_not_origin_parent.png")
+knitr::include_graphics("img/fork_upstream_is_not_origin_parent.jpeg")
 ```
 
 This is what happens when you do fork-and-clone and you *only* do fork-and-clone.