Papers › FlowTok: Flowing Seamlessly Across Text and Image Tokens

FlowTok: Flowing Seamlessly Across Text and Image Tokens

13 Mar 2025arXiv:2503.10772archive 2025-07-28

Ju He, Qihang Yu, Qihao Liu, Liang-Chieh Chen

Bridging different modalities lies at the heart of cross-modality generation. While conventional approaches treat the text modality as a conditioning signal that gradually guides the denoising process from Gaussian noise to the target image modality, we explore a much simpler paradigm-directly evolving between text and image modalities through flow matching. This requires projecting both modalities into a shared latent space, which poses a significant challenge due to their inherently different representations: text is highly semantic and encoded as 1D tokens, whereas images are spatially redundant and represented as 2D latent embeddings. To address this, we introduce FlowTok, a minimal framework that seamlessly flows across text and images by encoding images into a compact 1D token representation. Compared to prior methods, this design reduces the latent space size by 3.3x at an image resolution of 256, eliminating the need for complex conditioning mechanisms or noise scheduling. Moreover, FlowTok naturally extends to image-to-text generation under the same formulation. With its streamlined architecture centered around compact 1D tokens, FlowTok is highly memory-efficient, requires significantly fewer training resources, and achieves much faster sampling speeds-all while delivering performance comparable to state-of-the-art models. Code will be available at https://github.com/bytedance/1d-tokenizer.

PaperPDFCodeCode Syntology ranMethod as code

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 9 code samples harvested from 1 repository linked to this paper: 6 ran (of which 6 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified; every one of the 6 samples that ran constructed an object rather than computing a result. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 9 samples from 1 repository, 6 ran (6 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.

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

bytedance/1d-tokenizer officialmentioned in papermentioned on GitHubpytorchSyntology: 9 samples, 6 ran (0 instrument-failed) · 3 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.

Code Syntology ran Syntology

9 samples harvested: 6 ran (of which 6 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified; every one of the 6 samples that ran constructed an object rather than computing a result. “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.

6ran
3unverified

Licence: 0 of the 9 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 bytedance/1d-tokenizer. “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”. For 3 samples that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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.

bytedance/1d-tokenizer official repository 9 samples, 6 ran (0 instrument-failed) · 3 unverified
Conv2dSame in 7 papers modeling/titok.py ran fingerprinted Apache-2.0 (permissive) · 9c740c7fb2d9eb1a · report fixture: returned Conv2dSame · level recorded 2026-09-22
DiagonalGaussianDistribution in 7 papers modeling/titok.py ran Apache-2.0 (permissive) · 656f15a0445c5293 · report fixture: returned DiagonalGaussianDistribution · level recorded 2026-09-22
ResidualAttentionBlock in 38 papers modeling/titok.py ran Apache-2.0 (permissive) · f9805e2cf90696a2 · report fixture: returned ResidualAttentionBlock · level recorded 2026-09-22
ResnetBlock in 49 papers modeling/titok.py ran Apache-2.0 (permissive) · 34247def2368ea75 · report fixture: returned ResnetBlock · level recorded 2026-09-22
TiTokDecoder modeling/titok.py ran Apache-2.0 (permissive) · b3a00367dff48d07 · report fixture: returned TiTokDecoder · level recorded 2026-09-22
VectorQuantizer in 26 papers modeling/titok.py ran Apache-2.0 (permissive) · c604f5049ddf0f34 · report fixture: returned VectorQuantizer · level recorded 2026-09-22
TiTok modeling/titok.py unverified Apache-2.0 (permissive) · 2f5ef3dff7b3cad2 · report
TiTokEncoder modeling/titok.py unverified Apache-2.0 (permissive) · f96834950f20c5e0 · report
UpsamplingBlock modeling/titok.py unverified Apache-2.0 (permissive) · 66a99516de4e95bd · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for FlowTok (graph method: TiTok). 11 bricks; individually on a fixture: 8 ran (of which 6 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 1 where Syntology's instrument failed) · 3 unverified. The assembly has not been run end-to-end.

  1. TiTok entry · level 0 · unverified · 2f5ef3dff7b3cad2
  2. BaseModel helper · level 1 · ran · 331849d453e4a146
  3. DiagonalGaussianDistribution helper · level 1 · ran · 656f15a0445c5293
  4. TiTokDecoder helper · level 1 · ran · b3a00367dff48d07
  5. TiTokEncoder helper · level 0 · unverified · f96834950f20c5e0
  6. VectorQuantizer model · level 1 · ran · c604f5049ddf0f34
  7. ResidualAttentionBlock helper · level 1 · ran · f9805e2cf90696a2
  8. _expand_token helper · level 1 · ran · our draft was wrong · 8a18fd0e92a888ed
  9. Conv2dSame helper · level 1 · ran · 9c740c7fb2d9eb1a
  10. ResnetBlock helper · level 1 · ran · 34247def2368ea75
  11. UpsamplingBlock helper · level 0 · unverified · 66a99516de4e95bd

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2503.10772") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

DenoisingImage to textSchedulingText Generation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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