firecrawl-anydoc
Convert Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, and PDF files into clean GitHub-Flavored Markdown. Python bindings for the anydoc Rust crate, built by Firecrawl. Also available as a hosted API through Firecrawl Parse, which adds our OCR models for the scanned pages anydoc can't read on its own.
Every format parses into one shared document model and renders through a single Markdown serializer, so headings, tables, lists, and footnotes come out the same no matter which format goes in. Conversion releases the GIL, so other threads keep running. Type stubs ship with the package.
pip install firecrawl-anydoc
The package installs as firecrawl-anydoc and imports as anydoc.
Supported formats
| Format | Extensions |
|---|---|
| Word | .doc, .docx, .docm |
| PowerPoint | .ppt, .pps, .pot, .pptx, .pptm, .ppsx, .ppsm |
| Excel | .xls, .xlsx, .xlsm, .xlsb |
| OpenDocument | .odt, .ods, .odp |
| Rich Text Format | .rtf |
| EPUB | .epub |
| CSV | .csv |
.pdf |
Usage
import anydoc
# From a file path:
markdown = anydoc.to_markdown("report.docx")
# From bytes, with the format detected from the content:
markdown = anydoc.to_markdown_bytes(data)
# Or name it, which signature-less formats (CSV) need:
markdown = anydoc.to_markdown_bytes(data, "csv")
# Or stop at the document model, which also carries embedded assets:
document = anydoc.to_document(data)
Scanned pages
anydoc converts locally and does not do OCR, so a PDF with scanned or image-only pages raises NeedsOcrError. Opt in with ocr="hosted" to send that document to Firecrawl Parse. No signup needed. Set api_key or FIRECRAWL_API_KEY for higher limits.
markdown = anydoc.to_markdown("scan.pdf", ocr="hosted")
Errors
A conversion raises only when no complete Markdown could come out of the file. The exception type names what went wrong:
try:
return anydoc.to_markdown(path)
except (anydoc.EncryptedError, anydoc.UnsupportedError) as error:
# No document comes out of these, so record the file and take the next one.
unconverted.append((path, type(error).__name__))
return None
| Exception | Raised when |
|---|---|
UnsupportedError |
Unknown format, or one that cannot be converted |
NeedsOcrError |
Scanned or image-only pages of a PDF, listed in pages |
MalformedError |
Structurally unusable: no meaningful content could be extracted |
EncryptedError |
Encrypted or password-protected |
ResourceLimitError |
Crossed a fixed safety limit (decompression, nesting, node count) |
MissingPartError |
A part required for any meaningful output is absent |
HostedError |
ocr="hosted" could not get the document through Firecrawl Parse |
OSError |
The file could not be read, from to_markdown only |
Every conversion failure subclasses anydoc.ConvertError, so catching that handles all of them at once. MalformedError.part and MissingPartError.part name the package part at fault, ResourceLimitError.limit names the limit crossed, and str(error) carries the whole message. A format argument naming no supported format raises ValueError.
Format detection
The format is read from the file content, using the marker its specification designates: the PDF header, the RTF open group, OLE stream names, the ZIP package mimetype and content types. CSV has no such marker, so detection returns None for it and the extension, or an explicit format, names it instead.
anydoc.format_from_bytes(data) # 'docx', or None when nothing matches
anydoc.format_from_extension(".pptm") # 'pptx'
anydoc.format_from_path("report.odt") # 'odt'
Images and embedded objects
Markdown cannot embed bytes, so an embedded image renders as its alt text while the bytes stay on document.assets, tagged with a media type and the part they came from. Images that carry an external URL render as ordinary Markdown images.
Full behavior notes and benchmarks live in the repository README.
License
Metadata
Release files for firecrawl-anydoc 0.2.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| firecrawl_anydoc-0.2.4.tar.gz | 270.7 kB | With provenance | Details for firecrawl_anydoc-0.2.4.tar.gz |
Built distributions (wheels)
Total release size: 24.5 MB
Release files / firecrawl_anydoc-0.2.4.tar.gz
| Download URL | firecrawl_anydoc-0.2.4.tar.gz |
|---|---|
| Size | 270.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3e29460272fea81cde08fd5af11f6b0f1ff05919214ddc939867f72362c83032
|
|
BLAKE2b-256 checksum How to use checksums |
3554ee43b1661a954e53eaed85878a7ccc37ed73e02e6577bb26437ec5f9de94
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logRelease files / firecrawl_anydoc-0.2.4-cp310-abi3-win_amd64.whl
| Download URL | firecrawl_anydoc-0.2.4-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 3.6 MB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
7c9ffc81946e6954c124560ed1d395e0103a1a08fdc0f6be382e2f35daf6dbc9
|
|
BLAKE2b-256 checksum How to use checksums |
65346d54fed906055e5507dd94efd63f4a05021f103dc684ea62a3b0876b7595
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logRelease files / firecrawl_anydoc-0.2.4-cp310-abi3-musllinux_1_2_x86_64.whl
| Download URL | firecrawl_anydoc-0.2.4-cp310-abi3-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 3.7 MB |
| Tags | CPython 3.10 Linux musl 1.2+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
e57c79093c1592929dd8dfaf6c60b49eefe631721d96fb833c3f465472b37b9f
|
|
BLAKE2b-256 checksum How to use checksums |
cb2950c52b0ea5dd645aea6d195da913c8d9e136601eec465bd9a590edd250c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logRelease files / firecrawl_anydoc-0.2.4-cp310-abi3-musllinux_1_2_aarch64.whl
| Download URL | firecrawl_anydoc-0.2.4-cp310-abi3-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 3.4 MB |
| Tags | CPython 3.10 Linux musl 1.2+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
dd162b5eb64478fcf02f53abe7765e26f4350ba657f36c25f055c4cc3dbade0a
|
|
BLAKE2b-256 checksum How to use checksums |
1428b4d0d3c5345cdd65c0b9113c6e6ff1b717fe360dccb658db2a9952315f9c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logRelease files / firecrawl_anydoc-0.2.4-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | firecrawl_anydoc-0.2.4-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 3.5 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
0e5aed01bf6d4e5c588d3363888293f2ceeb9feb00449a32e0ba993797cf0bd3
|
|
BLAKE2b-256 checksum How to use checksums |
fc16feeca9705bfdb237f1cb69ede0b373b144c0d51df4297e595a74b815557e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logRelease files / firecrawl_anydoc-0.2.4-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | firecrawl_anydoc-0.2.4-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 3.3 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
17720ba093820654162891d7995fd2dbae948b16fe1c174ba799bddfc0b92ad6
|
|
BLAKE2b-256 checksum How to use checksums |
77b55784fc514f58ca19328faee701d2cc2e25961389c2d4908b2a51a1071ee4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logRelease files / firecrawl_anydoc-0.2.4-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | firecrawl_anydoc-0.2.4-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 3.3 MB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
b2a01eecaa0b99f99ff6749a098f8c7a5250d41db9c53673eb93536ad575bfed
|
|
BLAKE2b-256 checksum How to use checksums |
597d4b2a466c8953af3b9d94471081b04ce8636680111402d2140105f98c02e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logRelease files / firecrawl_anydoc-0.2.4-cp310-abi3-macosx_10_12_x86_64.whl
| Download URL | firecrawl_anydoc-0.2.4-cp310-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 3.4 MB |
| Tags | CPython 3.10 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
e3745a8b108d6575beafd37bcefe52e3f6c7ab44138e05cbdf4c6adf63caba84
|
|
BLAKE2b-256 checksum How to use checksums |
25f15616b8d703b2bf5688eda86ede4b35620356d9c60346fe2d3efbec2a872d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logSecurity for firecrawl-anydoc 0.2.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 8 files in this release have been uploaded with provenance metadata.
Attestation for firecrawl_anydoc-0.2.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.