scrapeMM: Multimodal Web Retrieval
Simple web scraper to asynchronously retrieve webpages and access social media contents, fetching text along with media, i.e., images and videos.
This library aims to help developers and researchers to easily access multimodal data from the web and use it for LLM processing.
Setup
- If you want to download videos: Then, the installation of ffmpeg is highly recommended.
In Conda, you can install it with
conda install -c conda-forge ffmpeg. Platforms like YouTube and Facebook serve video and audio as separate streams, and merging them needs ffmpeg. Without it, videos are downloaded without sound. scrapeMM also normalizes downloaded videos into a format browsers can play; that step additionally needsffprobe, which ships with a full ffmpeg install (theimageio-ffmpegpackage providesffmpegonly). - Install Playwright dependencies (used by multiple integrations) running
playwright install(add--forceif an already installed version needs an update).
Configure
To set the API secrets, run
from scrapemm import configure_secrets
configure_secrets()
To set the Firecrawl URL, run
from scrapemm import update_config
update_config(firecrawl_url="your_url")
A single Firecrawl instance is the throughput ceiling of the whole pipeline, so you can point scrapeMM at several of them. It probes all of them at startup, spreads its scrapes across those that respond, and retries a busy instance on another one instead of waiting:
update_config(firecrawl_urls=["http://host-a:3002", "http://host-b:3002"])
Platform Cookies
Some content is only served to a logged-in session. Set the respective cookie via
configure_secrets() (or override_secret("<name>")) to reach it:
| Secret | Unlocks |
|---|---|
facebook_cookie |
Facebook posts that require login |
instagram_cookie |
Age-restricted Instagram posts ("can't be seen by certain audiences") |
Facebook hides posts that fact-checkers flagged as false information behind an interstitial that yt-dlp cannot read. scrapeMM falls back to reading the video straight out of the page source in that case, so flagged posts stay retrievable.
Archive.today Access
Archive.today guards its snapshot pages with a Google reCAPTCHA, and a solved one unlocks them for only about five minutes. scrapeMM does not solve CAPTCHAs, so instead of waiting for you at the moment of each request it collects work for your next solve:
- A snapshot that was retrieved before is served from a permanent cache — a capture never changes, and only its page is gated, so retrieving it once settles it for good.
- Otherwise scrapeMM fetches the page with the stored session. Media comes from ungated subdomains, so images and videos download with no session at all.
- If the page is gated, the request fails immediately with a
CaptchaEncounteredErrorand the URL goes into a buffer. Nothing blocks. - When you solve the CAPTCHA, everything buffered is retrieved and cached within those
five minutes:
python scripts/configure_archive_today.py(add a number of seconds to wait, e.g.900, when running headless — it prints an SSH command to reach the browser window)
So the working rhythm is: let a batch run and collect misses, solve one CAPTCHA, then run
the batch again — the second time it is served from the cache. All mirrors (archive.is,
archive.ph, …) share one session and one cache.
from scrapemm import (get_archive_today_buffer, clear_archive_today_buffer,
retrieve_buffered_archive_today, count_cached_archive_today_pages)
get_archive_today_buffer() # URLs waiting for the next solve
count_cached_archive_today_pages() # how many pages are cached
retrieve_buffered_archive_today() # resume a drain the gate interrupted, session permitting
clear_archive_today_buffer() # forget the backlog
The buffer lives in archive_today_buffer.json and the pages in archive_today_pages/,
both in scrapeMM's config directory.
Two opt-ins sit beside this. update_config(archive_today_interactive_solve=True) restores
the old behaviour of opening the browser and waiting for you at the moment of a gated
request — reasonable for a one-off, attended retrieval, not for batches. And
update_config(archive_today_screenshot_fallback=True) serves the snapshot's screenshot
and metadata (not its text) when there is no session, so an unattended run gets something
rather than an error.
Usage
from scrapemm import retrieve
import asyncio
if __name__ == "__main__":
url = "https://www.snopes.com/fact-check/gauze-originate-from-gaza/"
result = asyncio.run(retrieve(url))
if result.success:
print(result.get())
else:
print(result.errors)
retrieve() returns a ScrapingResponse. Its result.get() returns the content in the requested
format; result.content gives access to every format that was produced along the way:
| Attribute | Type | Content |
|---|---|---|
result.content.html |
str |
The raw HTML code of the page |
result.content.markdown |
str |
The page text in Markdown, media referenced by hyperlink |
result.content.multimodal |
MultimodalSequence |
The page text in Markdown with all media downloaded and embedded |
Use output_format to tell scrapeMM which format you need (default: "multimodal"):
result = asyncio.run(retrieve(url, output_format="html"))
print(result.content.html)
The formats are produced one after another — HTML, then Markdown, then the MultimodalSequence —
and scraping stops as soon as the requested format is reached. So the earlier formats come along
for free (whenever the used retrieval method had access to them), while nothing beyond the
requested format is computed and media gets downloaded only for "multimodal". result.success
tells you whether the requested format could be produced.
scrapeMM will ask you for the API secrets needed for the integrations. You may skip them if you don't need them.
You will also be prompted to choose a password that is used to secure the secrets in an encrypted file.
Caching
Successful retrievals are cached in memory for 24 hours, so scraping the same URL again is
instantaneous. The cache is not persisted, i.e., it is empty again after the process ended.
result.from_cache tells you whether a response came from the cache.
To change the caching duration (in seconds) for the current process, run
from scrapemm import set_cache_ttl
set_cache_ttl(60 * 60) # cache for one hour
set_cache_ttl(0) # disable caching
Use update_config(cache_ttl=3600) instead to persist the duration across processes, and
clear_cache() to empty the cache. To bypass the cache for a single call, pass
retrieve(url, use_cache=False).
CAPTCHAs and Blacklisted Domains
Every scraped page is checked for CAPTCHA challenges (Cloudflare, reCAPTCHA, hCaptcha, DataDome,
AWS WAF, PerimeterX, and others). If a challenge was served instead of the page content, the
response carries a CaptchaEncounteredError and the URL's domain is put on a blacklist that is
persisted to blacklist.yaml in scrapeMM's config directory. Retrieving any URL of a blacklisted
domain then fails right away with an UnsupportedDomainError telling why the domain was
blacklisted.
from scrapemm import get_blacklisted_domains, unblacklist_domain, blacklist_domain
get_blacklisted_domains() # -> {"example.com": "Method decodo encountered a Cloudflare challenge. ..."}
unblacklist_domain("example.com") # Retrieve that domain again
blacklist_domain("example.com", "Paywalled") # Exclude a domain manually
A domain gets blacklisted only if all retrieval methods failed, so a CAPTCHA on one method does not exclude a domain that another method can still scrape. Blacklisting applies to the registrable domain, i.e., including all of its subdomains.
Automatic blacklistings expire after 7 days: CAPTCHA gates are often transient (a burst of parallel requests can trigger one on a domain that is perfectly retrievable an hour later), so excluding a domain forever would quietly erode coverage over time. Change the duration with
update_config(blacklist_ttl=24 * 60 * 60) # Retry blacklisted domains after a day
update_config(blacklist_ttl=0) # Never expire
Domains you blacklist yourself via blacklist_domain() are permanent — they express a
decision, not an observation — and stay excluded until you call unblacklist_domain().
Domains that are served by an integration (perma.cc, archive.today, x.com, ...) are never
blacklisted automatically: their CAPTCHA gates are transient, so blacklisting would disable the
respective integration for good.
Speeding Up Retrieval
By default, scrapeMM tries its retrieval methods strictly one after another, so a slow method delays every method behind it by its full timeout budget. Hedging gives each method only a head start instead: once the delay elapses, the next method is launched alongside it, the first success wins, and the rest are cancelled. A method that fails early hands over immediately, without waiting out the delay.
result = asyncio.run(retrieve(url, hedging_delay=5)) # 5 s head start per method
Use update_config(hedging_delay=5) to enable it process-wide. Hedging is disabled by default
because it duplicates work — and, for paid methods such as Decodo, duplicates billable requests.
How it works
Input: Output:
URL (string) --> retrieve() --> MultimodalSequence
The MultimodalSequence is a sequence of Markdown-formatted text and media provided by the ezMM library.
Web scraping is done with Firecrawl and Decodo.
Media is collected from <img> and <video> tags, from CSS background images, and from
embedded players of the common video platforms (an <iframe> pointing at YouTube, Vimeo,
Dailymotion, …), which are downloaded with yt-dlp. max_video_size caps every one of those
downloads just like it caps the ones of the platform integrations; oversized videos are skipped
without downloading a byte whenever the server announces a Content-Length.
Images are taken at their highest available resolution: srcset candidates are compared, and
lazy-loading attributes (data-src, data-lazy-src, data-original, …) are honoured, so pages
that ship a placeholder in src still yield their real media. Media references are resolved
against the page URL, no matter whether they are absolute, protocol-relative (//cdn/x.jpg),
root-relative (/x.jpg) or document-relative (img/x.jpg).
Supported Platforms
Social Media
- ✅ X/Twitter
- ✅ Telegram
- ✅ Bluesky
- ✅ TikTok
- ✅ YouTube
- ✅️ Instagram: works for most content
- ✅ Threads: posts only (profiles TBD)
- ✅ Reddit: posts only
Archiving Services
- ✅ Perma.cc
- ✅ Archive.today: Rarely ending up in TimeoutErrors
- ✅ MediaVault (mvau.lt)
- ✅ Internet Archive (web.archive.org)
- ✅ AwesomeScreenshot.com
- ✅ Ghostarchive (ghostarchive.org)
Release files for scrapeMM 0.8.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| scrapemm-0.8.3.tar.gz | 113.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scrapemm-0.8.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 245.1 kB
Release files / scrapemm-0.8.3.tar.gz
| Download URL | scrapemm-0.8.3.tar.gz |
|---|---|
| Size | 113.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c18d5705cc7ca7739968c0e964e02f8643e57014e8ae0994a8a7bfd34f851226
|
|
BLAKE2b-256 checksum How to use checksums |
04f08dd648cf36b59ee4d5fdc13f946227f3dd77f261a291af78a417fb304d91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Release files / scrapemm-0.8.3-py3-none-any.whl
| Download URL | scrapemm-0.8.3-py3-none-any.whl |
|---|---|
| Size | 131.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dbffa0f3205fdd1d45f6cf07896cdda4933a573a22d0c355f1be6b3cc5cc95da
|
|
BLAKE2b-256 checksum How to use checksums |
d4df05755a9f83099554d3af58be840e7b6729cac99f9b7c87519849d9ec3fff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|