Data-Juicer

Data processing system for foundation models with over 200 composable operators for multimodal data.

Open SourceSelf HostedOffline Capable
0.0 (0)

About

Data-Juicer treats training data preparation as composable infrastructure: more than 200 operators for cleaning, filtering, deduplicating, synthesizing, and analyzing data chain together in declarative recipe files, covering text, image, audio, and video, including dedicated processing for embodied AI and vision language action models. The system scales from a laptop to clusters through native Ray integration, and the team reports processing 70 billion samples in about two hours on 6,400 cores across 50 Ray nodes. A sandbox module supports data and model co-development experiments, and a hub collects more than 50 community recipes for reproducing known dataset pipelines. Alibaba Cloud has integrated the project into its PAI machine learning platform, which anchors it in production use. Installation is pip install py-data-juicer or Docker, most operators run on CPU with optional GPU acceleration for the model-based ones, and the codebase is Apache 2.0 with about 6,800 GitHub stars and a v1.5.4 release in July 2026. It suits teams curating multimodal corpora who want reproducible configs instead of one-off scripts.

Should you use Data-Juicer?

Pick it when

Pick it when you curate mixed text, image, audio, or video corpora and want cleaning, filtering, dedup, and synthesis defined in versioned recipe files that run on a laptop first and then scale out across a Ray cluster.

Look elsewhere when

For text-only web crawl pretraining, DataTrove is narrower and ships the FineWeb config plus a Slurm executor, and on GPU clusters where dedup is the bottleneck NeMo Curator fits better. For a small fine-tuning set, 200 operators is more system than you need.

Alternatives to Data-Juicer

  • DataTrove

    Text only, but ships the full FineWeb pipeline and a Slurm executor; Data-Juicer covers images, audio, and video and leans on Ray instead.

  • NeMo Curator

    Moves dedup and classification onto GPUs with RAPIDS for large speedups, but its GPU path needs Linux, CUDA 12, and about 16 GB of GPU memory where Data-Juicer runs mostly on CPU.

  • Cleanlab

    Finds mislabeled examples in labeled datasets, a job Data-Juicer's filters do not target; much smaller scope, runs locally on CPU.

Reviews (0)

Leave a Review

No reviews yet. Be the first to review!

Details

Price
Free
Platform
Local/Desktop
Difficulty
Intermediate (3/5)
License
Apache-2.0
Added
Jul 29, 2026

Tags