Practical overview
When it fits
Use Cryptofeed when a Python application needs a common event-handling layer across supported exchange feeds, or when exchange data must be delivered to callbacks, storage systems or a replayable capture.
Who it is for
- Python developers building applications that ingest market data from multiple cryptocurrency exchanges.
- Analytics and data-pipeline teams that need standardized exchange events for processing or storage.
- Researchers or developers recording exchange feeds for later replay.
Documented uses
- Collect trade, ticker, book and other supported public market-data events.
- Pass standardized updates to asynchronous client callbacks.
- Aggregate selected exchange feeds into a synthetic NBBO update.
- Route events through supported storage or messaging backends.
- Record feed data to pcap files for later replay.
Requirements & limits
The project is open source and available from PyPI. Its README specifies Python 3.13 or later and displays an AGPL license badge linked to a license file.
- WebSockets are used where available; REST polling is used otherwise.
- Supported exchanges and channels vary, and some feeds provide only partial L2 or L3 order-book depth.
- Callbacks must be asynchronous unless wrapped with the provided ExecutorCallback for synchronous handling.
- Optional dependencies depend on the selected backend.
- Trade events report the taker’s side, including for exchanges that report the maker’s side.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install Cryptofeed from PyPI
Install the library in a Python environment before configuring exchange feeds or storage backends.
Before you start
- Python 3.13 or later
- A Python environment with pip
Steps
Install the package with pip install cryptofeed.
If you need the optional dependencies for all backends, install with pip install cryptofeed[all].
Expected outcome
Cryptofeed is installed; you can proceed to configure FeedHandler subscriptions and callbacks in your application.
Guide limitations
- Backend-specific dependencies may be installed individually instead of using the all-dependencies extra.
- This installation procedure does not configure or run an exchange feed.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 16 October 2026
- Original website title
- bmoscon/cryptofeed · Official homepage title · retained in its source language

