Multimodal Models

Multimodal models connect text with images, audio, video, or structured signals. In generative systems they support captioning, document extraction, visual question answering, moderation, accessibility, and tool-augmented workflows. Vision-language models are the most common case in this wiki.

Encoder to language model

A common pattern is modality encoder -> projection/alignment -> language model. Contrastive models align image and text embeddings; generative VLMs condition token generation on visual features. Structured output is often needed when perception feeds software, and prompting must specify what visual evidence counts.

PatternMechanismTypical use
Dual encoderencode each modality into comparable embeddingsretrieval, matching, zero-shot classification
Cross-attention modellet text tokens attend to visual/audio featurescaptioning, question answering, document extraction
Token-unified modelrepresent multiple modalities as token streamsmultimodal generation or reasoning
Tool-mediated systemcall OCR, ASR, vision, or search tools around a modelauditable workflows with specialized components

The modality boundary matters. If a document extraction system fails, the error may come from OCR, layout parsing, visual perception, language reasoning, or schema formatting. Good evaluations isolate those layers instead of scoring only the final JSON.

Product patterns

PatternExampleImportant checks
Visual question answering”Does this dashboard show revenue below target?“chart reading, units, visible evidence.
Document extractioninvoice fields from a scanOCR quality, layout, schema validation.
Image moderationclassify unsafe uploaded imagethresholding, appeals, false positives.
Multimodal RAGretrieve images or pages, then answer with citationssource provenance and visual grounding.
Audio assistanttranscribe and summarize a meetingspeaker attribution and data privacy.
Tool-mediated workflowOCR tool -> language model -> validatorerror attribution across components.

An extraction contract

{
  "input": ["invoice_scan.png", "Extract supplier, date, total, currency"],
  "output_schema": { "supplier": "string", "total": "number", "currency": "string" },
  "validation": ["required_fields", "total_matches_line_items"]
}

This contract is deliberately explicit about validation. A multimodal model may read the total incorrectly because the image is blurry, because OCR split the currency symbol, or because the language model inferred a plausible total from line items. The downstream system should not treat the final JSON as ground truth without checks.

Evaluation

Evaluate by modality and by degradation. For images, slice by resolution, blur, rotation, screenshots, handwriting, tables, and diagrams. For audio, slice by noise, accents, overlapping speakers, and domain vocabulary. For video, slice by temporal localization and whether the relevant event is visible. Also test abstention: if the image is unreadable, the model should say so rather than fill gaps from prior knowledge.

Multimodal systems are especially prone to hidden hallucination, because final text can sound confident even when visual evidence was weak. Require evidence references for high-stakes extraction and avoid asking the model to infer invisible attributes.

Caveats

Perception errors and language errors look similar in final text. Evaluate by modality, image quality, layout, language, and refusal on unreadable inputs. Also track whether the model uses visible evidence or fills gaps from prior knowledge, because fluent answers can hide weak visual grounding. Privacy risk is higher because images and audio can contain incidental bystanders, screens, addresses, or voices that the user did not intend to expose.

References