Papers › Infinity-MM: Scaling Multimodal Performance with Large-Scale and High-Quality Instruction Data

Infinity-MM: Scaling Multimodal Performance with Large-Scale and High-Quality Instruction Data

24 Oct 2024arXiv:2410.18558archive 2025-07-28

Shuhao Gu, Jialing Zhang, Siyuan Zhou, Kevin Yu, Zhaohu Xing, Liangdong Wang, Zhou Cao, Jintao Jia, Zhuoyi Zhang, YiXuan Wang, Zhenchong Hu, Bo-Wen Zhang, Jijie Li, Dong Liang, Yingli Zhao, Songjing Wang, Yulong Ao, Yiming Ju, Huanhuan Ma, Xiaotong Li, Haiwen Diao, Yufeng Cui, Xinlong Wang, Yaoqi Liu, Fangxiang Feng, Guang Liu

Recently, Vision-Language Models (VLMs) have achieved remarkable progress in multimodal tasks, and multimodal instruction data serves as the foundation for enhancing VLM capabilities. Despite the availability of several open-source multimodal datasets, limitations in the scale and quality of open-source instruction data hinder the performance of VLMs trained on these datasets, leading to a significant gap compared to models trained on closed-source data. To address this challenge, we introduce Infinity-MM, a large-scale multimodal instruction dataset. We collected the available multimodal instruction datasets and performed unified preprocessing, resulting in a dataset with over 40 million samples that ensures diversity and accuracy. Furthermore, to enable large-scale expansion of instruction data and support the continuous acquisition of high-quality data, we propose a synthetic instruction generation method based on a tagging system and open-source VLMs. By establishing correspondences between different types of images and associated instruction types, this method can provide essential guidance during data synthesis. Leveraging this high-quality data, we have trained a 2-billion-parameter Vision-Language Model, Aquila-VL-2B, which achieves state-of-the-art (SOTA) performance among models of similar scale. The data is available at: https://huggingface.co/datasets/BAAI/Infinity-MM.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 6 code samples harvested from 1 repository linked to this paper: 5 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 6 samples from 1 repository, 5 ran (5 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

LLaVA-VL/LLaVA-NeXT mentioned in paperpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Visual Instruction Tuning (arXiv:2304.08485; that paper's own run record: 16 ran (of which 6 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 1 violated, 7 with no contract checked; 8 where Syntology's instrument failed) · 35 unverified); nothing checks that they implement this paper's method. report
flagopen/flagscale mentioned on GitHubpytorchApache-2.0Syntology: 6 samples, 5 ran (0 instrument-failed) · 1 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

6 samples harvested: 5 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

5ran
1unverified

Licence: 0 of the 6 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from flagopen/flagscale. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

flagopen/flagscale community (archive-listed) 6 samples, 5 ran (0 instrument-failed) · 1 unverified
flatten_dict_to_args flagscale/utils.py ran Apache-2.0 (permissive) · a946897a635a9ffa · report fixture: signature config_dict:dict/0/?, ignore_keys:list/1/str · returned list · level recorded 2026-09-24
make_headers flagscale/eval/robo.py ran Apache-2.0 (permissive) · 6c1f969a5ed98237 · report fixture: signature url:str/0/str, body:str/0/str, secret:str/0/str, include_content_type:bool/0/bool · returned dict · level recorded 2026-09-25
prepare_compress_methods flagscale/compress/combined_algo.py ran Apache-2.0 (permissive) · 9dd40bc51eb5b8b0 · report fixture: signature compress_cfg:dict/0/? · returned dict · level recorded 2026-09-24
prepare_config in 7 papers flagscale/compress/compressor.py ran Apache-2.0 (permissive) · ac0e60d70c14acfa · report fixture: signature config_path:str/0/str · returned DictConfig · level recorded 2026-09-24
start_server in 5 papers flagscale/eval/robo.py ran Apache-2.0 (permissive) · e580a09ddd5d3d19 · report fixture: signature model_name:str/0/str · returned Popen · level recorded 2026-09-24
auto_remote flagscale/serve/core.py unverified Apache-2.0 (permissive) · 0d33aaf712b41133 · report

Tasks

Image GenerationQuestion GenerationQuestion-GenerationVisual Question Answering (VQA)

Datasets

Introduced by this paper, per the archive.

Infinity-MM

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Image Generation TextAtlasEval Infinity-2B StyledTextSynth Clip Score 0.2727 #4 of 7 Archive leaderboard report
Image Generation TextAtlasEval Infinity-2B StyledTextSynth FID 84.95 #4 of 7 Archive leaderboard report
Image Generation TextAtlasEval Infinity-2B StyledTextSynth OCR (Accuracy) 0.80 #4 of 7 Archive leaderboard report
Image Generation TextAtlasEval Infinity-2B StyledTextSynth OCR (Cer) 0.93 #4 of 7 Archive leaderboard report
Image Generation TextAtlasEval Infinity-2B StyledTextSynth OCR (F1 Score) 1.42 #4 of 7 Archive leaderboard report
Image Generation TextAtlasEval Infinity-2B TextScenesHQ Clip Score 0.2346 #4 of 7 Archive leaderboard report
Image Generation TextAtlasEval Infinity-2B TextScenesHQ FID 71.59 #4 of 7 Archive leaderboard report
Image Generation TextAtlasEval Infinity-2B TextScenesHQ OCR (Accuracy) 1.06 #4 of 7 Archive leaderboard report
Image Generation TextAtlasEval Infinity-2B TextScenesHQ OCR (Cer) 0.88 #4 of 7 Archive leaderboard report
Image Generation TextAtlasEval Infinity-2B TextScenesHQ OCR (F1 Score) 1.74 #4 of 7 Archive leaderboard report
Image Generation TextAtlasEval Infinity-2B TextVisionBlend Clip Score 0.1979 #4 of 7 Archive leaderboard report
Image Generation TextAtlasEval Infinity-2B TextVisionBlend FID 95.69 #4 of 7 Archive leaderboard report
Image Generation TextAtlasEval Infinity-2B TextVisionBlend OCR (Accuracy) 2.98 #4 of 7 Archive leaderboard report
Image Generation TextAtlasEval Infinity-2B TextVisionBlend OCR (Cer) 0.83 #4 of 7 Archive leaderboard report
Image Generation TextAtlasEval Infinity-2B TextVsionBlend OCR (F1 Score) 3.44 #4 of 7 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections