diff --git a/sources/academy/webscraping/api_scraping/general_api_scraping/handling_pagination.md b/sources/academy/webscraping/api_scraping/general_api_scraping/handling_pagination.md
index d2a87ffc9..c54b2ffa8 100644
--- a/sources/academy/webscraping/api_scraping/general_api_scraping/handling_pagination.md
+++ b/sources/academy/webscraping/api_scraping/general_api_scraping/handling_pagination.md
@@ -19,7 +19,7 @@ If you've never dealt with it before, trying to scrape thousands to hundreds of
 
 The most common and rudimentary form of pagination is simply having page numbers, which can be compared to paginating through a typical e-commerce website.
 
-![Amazon pagination](https://apify-docs.s3.amazonaws.com/master/docs/assets/tutorials/images/pagination.jpg)
+![Amazon pagination](./images/pagination.png)
 
 This implementation makes it fairly straightforward to programmatically paginate through an API, as it pretty much entails just incrementing up or down in order to receive the next set of items. The page number is usually provided right in the parameters of the request URL; however, some APIs require it to be provided in the request body instead.
 
diff --git a/sources/academy/webscraping/api_scraping/general_api_scraping/images/pagination.png b/sources/academy/webscraping/api_scraping/general_api_scraping/images/pagination.png
new file mode 100644
index 000000000..e5833354d
Binary files /dev/null and b/sources/academy/webscraping/api_scraping/general_api_scraping/images/pagination.png differ