Extract from Drive, SharePoint, S3, and more
The /sources page names every place a document can live before txtfetch reads it. It states which ones hand over a URL, and which need a file upload.
https://txtfetch.com/changelog/
What shipped, and when.
Every entry below is dated to the commit that shipped it, and links to the page that proves it. Three entries are corrections, not features — we'd rather list those than hide them.
Subscribe: /changelog.xml
September 2026
A free tool to clean up damaged extracted text
Paste text that came out of any extractor and see the damage signals. Each one links to the fix that explains it, and nothing is uploaded.
What pgvector, Pinecone, Qdrant, Chroma, and Weaviate need next
txtfetch stops at extracted text. /ingest covers the chunk, embed, and upsert step for five vector stores, cited and dated.
How txtfetch compares to five open-source parsers
/compare/libraries checks txtfetch against Docling, MarkItDown, PyMuPDF4LLM, Marker, and MinerU on licence, GPU need, format coverage, and OCR.
Document-language pages, with the honest OCR limit stated
/languages covers nine document languages: legacy encodings, chunking risk, and where OCR support actually stops.
August 2026
Stopped promising guaranteed reading order on multi-column PDFs
/solutions claimed txtfetch always kept multi-column PDFs in reading order. It does not: the engine gets most PDFs right, and /fixes/columns-out-of-order covers the rest. The page now says so.
Wire txtfetch into n8n, Zapier, Make, Airflow, or S3 and Lambda
No plugin ships for any of them. /integrations shows the HTTP step each platform already has, pointed at txtfetch.
An honest answer to 'why not self-host Tika?'
Apache Tika is free. /compare/self-hosted-tika shows the pinned versions, the from-source Tesseract build, and the runtime limits behind the question.
An extraction glossary
/glossary defines PDF text layers, OCR, mojibake, OOXML, and chunking in plain language. Each term links to its full page.
Raw parser output next to txtfetch's output, word for word
/diff shows ten committed documents with the raw parser text next to the corrected text, with every difference marked.
Audio and video get their own extraction page
/extract/captions states exactly what comes back from an .srt, .vtt, .mp4, .mp3, or .mkv file. A file with no caption track and no tag data returns an error, not an empty success.
Corrected the '1,000+ formats' claim
That figure counted every media type Tika can detect, not every one it can parse. /formats/coverage now lists the real, checked count, measured against the exact jar this build ships.
One drop zone for any file type
/tools/file-to-text detects a file's real type from its bytes and extracts its text in the browser, with no upload.
Free readers for legacy Word, Excel, and PowerPoint files
/tools/doc-to-text reads the 97-2003 binary Office formats (.doc, .xls, .ppt) in the browser, alongside the existing DOCX/XLSX/PPTX tools.
Check whether a scan will OCR cleanly before you send it
/tools/image-ocr-check measures resolution, focus, skew, and inversion from a photo's actual pixels, in the browser.
Stopped claiming the API returns media metadata it has no field for
Copy on /tools/subtitles-to-text said the API returns a title, artist, duration, and codec for media files. It has no such field. A success carries the extracted text, the content type, the byte and character counts, and whether OCR ran.
Read .eml and Outlook .msg files, attachments included
/tools/email-to-text extracts a message and its attachments recursively, in the browser.
In-browser DOCX, XLSX, and PPTX readers
/tools/docx-to-text and its XLSX and PPTX siblings read modern Office files in the browser. No upload, no API call.
Every page on this site is also plain text
Append .md to any URL for a plain-text twin. /llms.txt indexes the whole site by section, and /llms-full.txt is the whole corpus in one file.
July 2026
A page for text that extracted but came out wrong
/fixes covers symptoms like mojibake, missing spaces, and scrambled columns: what causes each one, and how to fix it.
Use-case pages: RAG ingestion, search indexing, document workflows
/solutions shows the same API applied to different jobs, with the parts of the response each job actually uses.
Developer docs: quickstarts, async jobs, idempotency, errors
/docs covers authentication and both ways to call the API. It also covers response formats, async jobs and webhooks, idempotency keys, and the full error reference.
A public status page
/status shows current status and 90-day uptime history for the extraction API. No login is required.
A dedicated page for every format
/extract lists format-specific pages covering PDF, Office, email, HTML, images, and more, each with its own working curl.
what this page is
One hub, no roadmap.
This page has no roadmap section and no deprecation policy. The one fact worth stating about versioning: every endpoint lives under /v1. Everything else here already shipped.
Stop parsing. Start shipping.
Create an account and get an API key in minutes. The free Hobby plan needs no card.
Get started →