Sounds like this does a lot more than simply take a screenshot. It mentions removing cookie banners, ads, etc. which is an always moving target.

If you have one, very narrow specific use case, then maybe that’s not so bad. But sounds like a huge pain if you need that for any arbitrary site.

> Sounds like this does a lot more than simply take a screenshot. It mentions removing cookie banners, ads, etc. which is an always moving target.

Oh okay so it does:

chrome --load-extension=path/to/ublock --headless --screenshot https://website.com

Couldn't this be done with a headless Firefox and adblocker extensions?

I’m sure it could be. Just like I could bake an apple pie by first sowing wheat and planting apple trees.

Feels like Dropbox comment.

Browserless is not free for commercial use.

> instead of managing browser clusters, and handling all the corner cases

The cost with running a docker container is you have to manage that container. You’re paying with dev time not money.

Exactly this. We keep forgetting time and money that needs to be paid to a developer to setup and manage stuff.

I cant edit the above post but follow that command with a request for a screenshot like so:

    curl -X POST http://localhost:3000/screenshot \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com"}' \
  --output screenshot.png

And what commands do I run if I want to do 100 screenshots per second?

Not arguing as a part of this thread but as an aside.

Can chrome even take 100 screenshots a second? What would be the max? I think it's interesting.

Yeah that's basically just a 100 FPS video at that point lol

Well, for some users and uses, it's free. It seems they consider their small amount glue between docker and chrome a to be of commercial value. Still better than the original.

https://github.com/browserless/browserless/blob/main/LICENSE