Learn about the Docker images you can use as your actor's base. Choose the correct base image for your actor's type and requirements.
Apify provides several Docker images that can be used as a base for user actors.
All images come in two versions: the latest tag corresponds to the stable version and beta to images where we test new features. Use the beta version at your own risk.
Note that all Apify Docker images are pre-cached on Apify servers in order to speed up the actor builds and runs. The source code used to generate the images is available in the apify-actor-docker GitHub repository.
Node.js 16 on Alpine Linux (
apify/actor-node) - slim and efficient image, contains only the most elementary tools. Note that headless browsers (Puppeteer, Playwright) are not available in this image.
Node.js 16 + Puppeteer + Chrome on Debian (
apify/actor-node-puppeteer-chrome) - larger image with the Chromium and Google Chrome browsers and the
puppeteerlibrary bundled. With this image, you can use the
PuppeteerCrawler. Note that Chrome requires quite a lot of resources, therefore the actor should run with at least 2048 MB of memory.
Node.js 16 + Playwright + Chrome on Debian (
apify/actor-node-playwright-chrome) - similar to the
apify/actor-node-puppeteer-chromeimage, but it comes preinstalled the
playwrightautomation library instead of Puppeteer. With this image, you can use the
PlaywrightCrawler. This image also comes with a
For a full list of available images, see the Apify SDK Docker image guide. Note that some images available in the Apify UI can be marked as deprecated. This means that they should no longer be used for new projects and old projects are encouraged to migrate to one of the non-deprecated images.
The Apify API client for Python is preinstalled on these images.