Skip to main content


Learn how to write a comprehensive README to help users better navigate, understand and run public Actors in Apify Store.

  • It should also be a "template" for developers developing new public Actors so that they have a structure and guidance for writing the README.
  • The goal is to ensure that more people will understand and run their Actors.
  • Whenever you build an Actor, think of the original request/idea and the "use case" = "user need" it should solve, please take notes and share them with Apify, so we can help you write a blog post supporting your Actor with more information, more detailed explanation, better SEO.
  • Consider adding a video, images, and screenshots to your README to break up the text.
  • This is an example of an Actor with a README that corresponds well to the guidelines below:
  • Tip no.1: if you want to add snippets of code anywhere in your README, you can use Carbon.
  • Tip no.2: if you need any quick Markdown guidance, check out

🦾 No time for writing? Our README Generator will create a new README out of thin air following the template below ⬇️

What should you add to your Actor README?

Aim for sections 1–6 below and try to include at least 300 words. You can move the sections around to some extent if it makes sense, e.g. 3 might come after 6. Consider using emojis as bullet points or otherwise trying to break up the text.

  1. What does (Actor name) do?

    • in 1–2 sentences describe what the Actor does and what it does not do
    • consider adding keywords like API, e.g. Instagram API
    • always have a link to the target website in this section
  2. Why use (Actor name)? or Why scrape (target site)?

    • How it can be beneficial for the user
    • Business use cases
    • Link to a success story, a business use case, or a blog post.
  3. How much will it cost to scrape (target site)?

    • Simple text explaining what type of proxies are needed and how many platform credits (calculated mainly from consumption units) are needed for 1000 results.
    • This is calculated from carrying out several runs (or from runs saved in the DB).
    • Here’s an example for this section:

    How much will it cost me to scrape Google Maps reviews?

    Apify provides you with $5 free usage credits to use every month on the Apify Free plan and you can get up to 100,000 reviews from this Google Maps Reviews Scraper for those credits. This means 100k results will be completely free!
    But if you need to get more data or to get your data regularly you should grab an Apify subscription. We recommend our $49/month Starter plan - you can get up to 1 million Google Maps reviews every month with the $49 monthly plan! Or 10 million with the $499 Scale plan - wow!
  4. How to scrape (target site)

    • Link to "How to…" blogs, if one exists (or suggest one if it doesn't)

    • Add a video tutorial or GIF from an ideal Actor run.

    Tip: For better user experience, Apify Console automatically renders every YouTube URL as an embedded video player. Simply add a separate line with the URL of your YouTube video.

    • Consider adding a short numbered tutorial as Google will sometimes pick these up as rich snippets. Remember that this might be in search results, so you can repeat the name of the Actor and give a link, e.g.

    How to scrape a website - numbered tutorial

  5. Is it legal to scrape (target site)?

    • This can be used as a boilerplate text for the legal section, but you should use your own judgement and also customize it with the site name.

    Our scrapers are ethical and do not extract any private user data, such as email addresses, gender, or location. They only extract what the user has chosen to share publicly. We therefore believe that our scrapers, when used for ethical purposes by Apify users, are safe. However, you should be aware that your results could contain personal data. Personal data is protected by the GDPR in the European Union and by other regulations around the world. You should not scrape personal data unless you have a legitimate reason to do so. If you're unsure whether your reason is legitimate, consult your lawyers. You can also read our blog post on the legality of web scraping

  6. Input

    • Each Actor detail page has an input tab, so you just need to refer to that. If you like, you can add a screenshot showing the user what the input fields will look like.
    • This is an example of how to refer to the input tab:

    Twitter Scraper has the following input options. Click on the input tab for more information.

  7. Output

  8. Tips or Advanced options section

    • Share any tips on how to best run the Actor, such as how to limit compute unit usage, get more accurate results, or improve speed.

If you want some general tips on how to make GitHub README that stands out, check out these guides. Not everything in there will be suitable for an Apify Actor README, so you should cherry-pick what you like and use your imagination.

Build a Stunning README For Your GitHub Profile

How to Create a Beautiful README for Your GitHub Profile

Next up

If you followed all the tips described above, your Actor README is almost good to go! In the next lesson we will give you a few instructions on how you can create a tutorial for your Actor.