Serverless Chrome vs Splash

Overview

Splash

Stacks29

Followers36

Votes0

GitHub Stars4.2K

Forks516

Serverless Chrome

Stacks7

Followers25

Votes0

GitHub Stars2.9K

Forks280

Serverless Chrome vs Splash: What are the differences?

Developers describe Serverless Chrome as "Headless Chrome on AWS Lambda". The aim of this project is to provide the scaffolding for using Headless Chrome during a serverless function invocation. Serverless Chrome takes care of building and bundling the Chrome binaries and making sure Chrome is running when your serverless function executes. In addition, this project also provides a few "example" handlers for common patterns (e.g. taking a screenshot of a page, printing to PDF, some scraping, etc.). On the other hand, Splash is detailed as "Headless browser that executes JavaScript for people crawling websites". It is a headless browser that executes JavaScript for people crawling websites. It is open source and fully integrated with Scrapy and Portia. You can also use its API to integrate with any project that needs to render JavaScript pages.

Serverless Chrome and Splash belong to "Headless Browsers" category of the tech stack.

Serverless Chrome and Splash are both open source tools. It seems that Splash with 2.6K GitHub stars and 364 forks on GitHub has more adoption than Serverless Chrome with 2.02K GitHub stars and 205 GitHub forks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Detailed Comparison

Splash	Serverless Chrome
It is a headless browser that executes JavaScript for people crawling websites. It is open source and fully integrated with Scrapy and Portia. You can also use its API to integrate with any project that needs to render JavaScript pages.	The aim of this project is to provide the scaffolding for using Headless Chrome during a serverless function invocation. Serverless Chrome takes care of building and bundling the Chrome binaries and making sure Chrome is running when your serverless function executes. In addition, this project also provides a few "example" handlers for common patterns (e.g. taking a screenshot of a page, printing to PDF, some scraping, etc.)
Executes and renders JavaScript to scrape dynamic content; Its HTTP API receives URLs and responses with HTML contents	-
Statistics
GitHub Stars 4.2K	GitHub Stars 2.9K
GitHub Forks 516	GitHub Forks 280
Stacks 29	Stacks 7
Followers 36	Followers 25
Votes 0	Votes 0
Integrations
JavaScript Linux Scrapy Python Ubuntu Mac OS X	Serverless Yarn AWS Lambda

What are some alternatives to Splash, Serverless Chrome?

Playwright

It is a Node library to automate the Chromium, WebKit and Firefox browsers with a single API. It enables cross-browser web automation that is ever-green, capable, reliable and fast.

Puppeteer

Puppeteer is a Node library which provides a high-level API to control headless Chrome over the DevTools Protocol. It can also be configured to use full (non-headless) Chrome.

PhantomJS

PhantomJS is a headless WebKit scriptable with JavaScript. It is used by hundreds of developers and dozens of organizations for web-related development workflow.

HeadlessTesting

Headless Browser Cloud for Developers. Connect your Puppeteer and Playwright scripts to our Cloud. Automated Browser Testing with Puppeteer and Playwright in the Cloud.

jsdom

It is a pure-JavaScript implementation of many web standards, notably the WHATWG DOM and HTML Standards, for use with Node.js. In general, the goal of the project is to emulate enough of a subset of a web browser to be useful for testing and scraping real-world web applications.

CasperJS

CasperJS is a browser navigation scripting & testing utility written in Javascript for PhantomJS or SlimerJS.

SlimerJS

It allows you to manipulate a web page with an external Javascript script: opening a webpage, clicking on links, modifying the content... It is useful to do functional tests, page automation, network monitoring, screen capture etc.