head to head · open source
Browser Use vs recipe-scrapers
Browser Use has 119,977 GitHub stars, 13,371 forks, 421 open issues and last shipped 3 days ago. recipe-scrapers has 2,263 stars, 681 forks, 131 open issues and last shipped 2 days ago. Browser Use leads on adoption by 5,202% (119,977 vs 2,263 stars). Browser Use is written in Python under MIT; recipe-scrapers is written in Python under MIT. Browser Use has attracted 11% as many forks as stars, recipe-scrapers 30%. recipe-scrapers was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| Browser Use | recipe-scrapers | |
|---|---|---|
| GitHub stars | ★ 120K | ★ 2.3K |
| License | MIT | MIT |
| Written in | Python | Python |
| Last push | 2026-11-02 | 2026-11-03 |
| Forks | ⑂ 13K | ⑂ 681 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Browser Use if
- You weight community size — 120K stars and counting
- You want the MIT license terms
- Your stack matches Python
- You value the larger contributor base for long-term maintenance
pick recipe-scrapers if
- You want the recipe-scrapers feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Python
- You evaluated both and recipe-scrapers fits your workflow better
About Browser Use
Navigate the web like a human does. Find an available slot, pick a date and time, handle the CAPTCHA, and book a driving test. Explore more demos and prompts ↗ Which Browser Use do I need? Path 1: Fully Hosted Cloud: Scale up with a fully hosted agent and browser. Path 2: CLI: Automate your own browser tasks. Path 3: Python Library: Run the open source Browser Use agent locally from your own code. Quickstart Path 1: Fully Hosted Cloud Scale browser automation with our hosted agent, stealth browsers, and infrastructure for profiles, recordings, and data policies. Get started with the API ↗ New Google, GitHub, or…
read the full Browser Use overview →
About recipe-scrapers
================= recipe scrapers ================= .. image:: :target: :alt: Github .. image:: :target: :alt: Version .. image:: :target: :alt: PyPI Python Version .. image:: :target: unittests :alt: GitHub Actions Unittests .. image:: :target: :alt: Coveralls .. image:: :target: :alt: License Quick Links Documentation Supported Sites Contributing Guide Issue Tracker Share Project Ideas A Python package for extracting recipe data from cooking websites. Parses recipe information from either standard HTML structure, Schema markup (including JSON LD, Microdata, and RDFa formats) or OpenGraph metadata. The package…
read the full recipe-scrapers overview →
More in Data & Analytics
Related comparisons
More Data Extraction & Web Scraping projects
Compare either of these against the rest of the Data Extraction & Web Scraping field.
Frequently asked questions
Is Browser Use or recipe-scrapers more popular?
Browser Use has 119,977 GitHub stars and recipe-scrapers has 2,263. Browser Use has the larger community by that measure.
Are Browser Use and recipe-scrapers free?
Both are open source. Browser Use is licensed under MIT and recipe-scrapers under MIT. Neither carries a licence fee.
What is the difference between Browser Use and recipe-scrapers?
Browser Use is written in Python and recipe-scrapers in Python. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, Browser Use or recipe-scrapers?
Choose Browser Use if you want the larger community (119,977 stars) or its MIT licence terms. Choose recipe-scrapers if its feature set, stack or MIT licence fits better. Both are self-hostable.