{"id":465,"date":"2026-05-18T10:00:00","date_gmt":"2026-05-18T01:00:00","guid":{"rendered":"https:\/\/blog.hancom.com\/what-is-vlm-easily-understanding-from-vision-language-model-concepts-to-document-ai-applications\/"},"modified":"2026-07-16T15:21:39","modified_gmt":"2026-07-16T06:21:39","slug":"what-are-vision-language-models","status":"publish","type":"post","link":"https:\/\/blog.hancom.com\/en\/what-are-vision-language-models\/","title":{"rendered":"What is VLM? Easily Understanding from Vision Language Model Concepts to Document AI Applications"},"content":{"rendered":"\n

Have you ever experienced taking a picture of a receipt and having AI instantly read the amount, or summarizing key clauses from a contract image? <\/p>\n\n

The core technology behind these capabilities is VLM (Vision-Language Model, visual language model)<\/strong>. It is a multimodal AI technology that understands images and text together, and it has been rapidly gaining attention in the document processing field. In this article, we\u2019ll clearly break down what VLM is, how it differs from OCR (Optical Character Recognition) and LLM (Large Language Model), and how it connects to the RAG pipeline. <\/p>\n\n

<\/div>\n\n
\"Image<\/figure>\n\n
<\/div>\n\n

What is VLM?<\/strong><\/h2>\n\n
<\/div>\n\n

Basic Concepts of VLM (Vision-Language Model)<\/strong><\/strong><\/h3>\n\n

VLM is a multimodal AI model that processes both images and text.<\/strong><\/strong><\/p>\n\n

Traditional LLMs<\/strong> are structured to process only text input. When a document is provided, they can only read textual information and cannot interpret images or charts contained within as meaningful data. <\/p>\n\n

VLM<\/strong> takes this a step further, where a Vision Encoder converts images into vectors<\/strong>, which are then processed alongside the LLM. This structure allows it to understand both meaning and context by accepting visual information in addition to text as a single input. <\/p>\n\n

For example, if a sales graph image is input, an LLM cannot read the image, but a VLM can interpret it as “a bar graph showing a rise in Q3 sales compared to the previous quarter<\/strong>.”<\/p>\n\n

Representative models include LLaVA, Qwen, and Gemma, which are utilized for image captioning, visual question answering (VQA), and document understanding.<\/p>\n\n

<\/div>\n\n

How VLM Understands Images and Text<\/strong><\/h3>\n\n

VLM operates through the following flow: Image Input \u2192 Vision Encoder \u2192 Image Token Conversion \u2192 LLM Processing \u2192 Text Generation<\/strong>.<\/p>\n\n

When an image is input, the Vision Encoder<\/strong> extracts visual features. The extracted features pass through a Projector<\/strong> and are converted into Image Tokens that the LLM can process. <\/p>\n\n

Subsequently, these tokens are input into the LLM along with a text query to generate the final natural language response.<\/p>\n\n

<\/div>\n\n
\"Image<\/figure>\n\n
<\/div>\n\n

How the Vision Encoder Output Connects with LLM<\/strong><\/h3>\n\n

The structure of VLM consists of three elements: a Vision Encoder, a Projector, and an LLM<\/strong>. Image information is transformed into a format that the LLM can process through this pathway. <\/p>\n\n

Role of the Vision Encoder<\/strong><\/h4>\n\n

The Vision Encoder divides an image into small patches, encodes each into a vector, and outputs Visual Feature Vectors. ViT (Vision Transformer), which applies the transformer architecture to image processing, is a representative example. <\/p>\n\n

Projector for Image Information Transformation<\/strong><\/h4>\n\n

It converts the Vision Encoder’s output into image tokens that the LLM can understand. Depending on the implementation method, techniques such as Linear Projection or Cross-Attention are used. <\/p>\n\n

Role of the LLM<\/strong><\/h4>\n\n

The LLM, a large language model that generates text, receives both the image tokens converted by the projector and text tokens as input to generate natural language responses. For open-source VLMs, a common approach is to connect the Vision Encoder while maintaining the pre-trained LLM. <\/p>\n\n

<\/div>\n\n
\"Image<\/figure>\n\n
<\/div>\n\n

Why VLM is Necessary: LLM Limitations and Document AI Challenges<\/strong><\/h2>\n\n
<\/div>\n\n

LLM Limitations in Image and Document Processing<\/strong><\/h3>\n\n

LLMs, which process only text, have limitations in understanding visual information such as images, charts, and tables within documents as meaningful data. Information not expressed as text, like document formatting, tables, and figures, is difficult for LLMs to interpret directly. Inputting only text without a separate image processing step can lead to the loss of visual information. <\/p>\n\n

Problem of Structure Loss During Document Parsing<\/strong><\/h3>\n\n

When only text is extracted from PDF, HWP, or HWPX documents and fed into AI, structural information such as tables, paragraphs, and layouts can be lost. Common issues include broken merged cell structures or scrambled reading order in multi-column layouts. Contextual information embedded in images and charts is also frequently lost during this process. <\/p>\n\n

Why a Multimodal Approach is Necessary<\/strong><\/h3>\n\n

Text-based LLMs alone struggle to fully comprehend the visual information within documents. Just as humans interpret text by simultaneously examining layouts and figures, AI must also be able to understand visual information beyond text. Consequently, a multimodal approach that processes both images and language has emerged as a critical challenge in Document AI. <\/p>\n\n

<\/div>\n\n

Comparison of VLM, OCR, and LLM Differences<\/strong><\/h2>\n\n
<\/div>\n\n

OCR vs. VLM: Text Recognition vs. Image Understanding<\/strong><\/h3>\n\n

OCR (Optical Character Recognition) is a technology that recognizes characters within an image and converts them into text, whereas VLM is a technology that understands the entire visual information and context of an image and describes it in language.<\/strong><\/strong><\/p>\n\n

OCR extracts ‘what characters are in this image,’ while VLM interprets ‘what this image means.’ In a sales graph image, OCR only reads the axis label text, but VLM goes beyond reading text to explain the context, such as ‘a bar graph showing a rise in Q3 sales compared to the previous quarter.’ <\/p>\n\n

<\/div>\n\n

\ud83d\udcda Recommended Reading<\/strong><\/p>\n\n

\ud83d\udc49 What is OCR? From Core AI OCR Technology to Document Automation Utilization Guide <\/a><\/strong><\/p>\n\n

<\/div>\n\n

LLM vs. VLM: Text-Only vs. Multimodal<\/strong><\/h3>\n\n

Unlike LLMs, which only receive text input, VLMs receive both images and text, making them multimodal models that integrate and process visual and linguistic information.<\/p>\n\n

OCR, LLM, VLM Comparison at a Glance<\/strong><\/h4>\n\n
Category<\/strong><\/td>OCR<\/strong><\/td>LLM<\/strong><\/td>VLM<\/strong><\/td><\/tr>
Input<\/td>Image<\/td>Text<\/td>Image + Text<\/td><\/tr>
Processing Method<\/td>Character Recognition<\/td>Language Understanding, Generation<\/td>Integrated Visual and Language Understanding<\/td><\/tr>
Output<\/td>Extracted Text<\/td>Text<\/td>Extracted Text, Image Description, Question Answering<\/td><\/tr>
Image Understanding<\/td>Not Supported<\/td>Not Supported<\/td>Supported<\/td><\/tr><\/tbody><\/table><\/figure>\n\n
<\/div>\n\n

Differences from Traditional Computer Vision Models<\/strong><\/h3>\n\n

Unlike traditional computer vision models that perform only specific learned tasks, VLMs flexibly respond to various visual tasks through natural language instructions<\/strong>.<\/p>\n\n

However, for specialized tasks such as object detection and segmentation, dedicated CV models may sometimes exhibit higher accuracy.<\/p>\n\n

<\/div>\n\n

Limitations of Traditional CV Models<\/strong><\/h4>\n\n

Traditional computer vision models for tasks like Classification, Object Detection, and Segmentation are designed to perform specific learned tasks accurately and efficiently. While they show high performance in narrow task ranges, adding new tasks requires separate training data and fine-tuning. <\/p>\n\n

<\/div>\n\n

Scalability of VLM<\/strong><\/h4>\n\n

VLMs define tasks using natural language instructions. This allows a single model to handle a wide range of tasks<\/strong>, including image captioning, document understanding, and chart interpretation. In document recognition, it eliminates the need to connect individual models for OCR, layout analysis, and information extraction. Instead, text, tables, and key-value pairs can be obtained from an image at once, simplifying the pipeline and significantly reducing error propagation at each stage. <\/p>\n\n

<\/div>\n\n

VLM Limitations in Document AI and the Importance of Data Preprocessing<\/strong><\/h2>\n\n

Why VLM May Not Perform Well: Data Quality Issues<\/strong><\/h3>\n\n

While VLM performance itself is important, in actual production environments, the structural quality of input data often significantly impacts the results.<\/strong><\/p>\n\n

No matter how sophisticated the VLM model, accurate results cannot be achieved if the structure of the data extracted from the document is compromised. If only text is input without document structure information, the VLM struggles to determine whether the content is a title, body text, or part of a specific table cell. <\/p>\n\n

<\/div>\n\n

Why AI Performance Decreases When Document Structure is Broken<\/strong><\/h3>\n\n

If table cell relationships, paragraph hierarchies, and the positional relationships between images and text are lost when input into a VLM, the model may struggle to reliably interpret the semantic relationships within the document.<\/strong><\/p>\n\n

For example, if a document with a sales table under the title ‘Q3 Performance’ is converted to plain text without structure, the relational information between the title and the table can be weakened.<\/p>\n\n

Even in RAG pipelines, if only fragmented text with missing structure is retrieved, contextual connections can become unstable, increasing the likelihood of inaccurate answers or hallucinations.<\/p>\n\n

<\/div>\n\n

Impact of Document Data Quality on AI Results<\/strong><\/h3>\n\n

As VLM is a multimodal model that processes both images and text, the quality of the input document’s structure and context can affect the accuracy of the results<\/strong>.<\/p>\n\n

Especially for complex documents combining HWP, HWPX, PDF, and images, it is crucial to extract them while preserving table structures, paragraph hierarchies, and image positional relationships.<\/p>\n\n

Contextual information such as the relationship between titles and body text, the row and column structure of tables, and descriptions around images must be maintained for VLMs and LLMs to interpret documents more naturally.<\/p>\n\n

<\/div>\n\n
\"Hancom<\/a><\/figure>\n\n
<\/div>\n\n

Hancom Data Loader: Documents into AI-Understandable Data<\/strong><\/h2>\n\n

\ud83d\udda5\ufe0f Hancom Data Loader<\/strong><\/a><\/p>\n\n

<\/div>\n\n

Hancom Data Loader is a Document Layout Analysis (DLA) solution that addresses preprocessing challenges in Document AI systems.<\/p>\n\n

Resolves document structure loss issues. <\/strong>By directly parsing the original binaries of HWP and HWPX, it preserves metadata without data loss.<\/p>\n\n

Preserves tables and multi-column layouts. <\/strong>It preserves the original structure, including merged cells, borderless tables, and the reading order of multi-column layouts, extracting data at the cell level. This ensures that row and column relationships are maintained when input into VLMs or LLMs. <\/p>\n\n

Preserves text and object relationships.<\/strong> It utilizes Document Layout Analysis (DLA), a document layout analysis technology, to identify the positional relationships between text, images, and charts. Furthermore, it supports a pipeline that converts images into textual descriptions using VLM-based image captioning technology. (This feature is currently in the PoC stage; commercial release dates will be announced later.)<\/em> <\/p>\n\n

Converts unstructured documents into data. <\/strong>Scanned documents, PDFs containing images, and complex HWP\/HWPX layouts can be output in structured formats like JSON, depending on the document type and product configuration, making them suitable for AI training data preparation and RAG pipeline integration. <\/p>\n\n

\ud83d\udca1 Before building VLM and RAG pipelines, check your document preprocessing quality. <\/p>\n\n

\ud83d\udc49<\/strong> Explore Hancom Data Loader<\/strong><\/a><\/p>\n\n

<\/div>\n\n

VLM Frequently Asked Questions (FAQ)<\/strong><\/h2>\n
\n
\n
\n

Q1. What is the difference between VLM and LLM? <\/strong><\/h3>\n
\n\n

VLM is a multimodal AI model that processes both images and text. Unlike traditional LLMs, which operate primarily on text, VLMs can process image inputs alongside text to generate responses based on the relationship between visual information and text. <\/p>\n\n<\/div>\n<\/div>\n

\n

Q2. What is the difference between document parsing and OCR? <\/strong><\/h3>\n
\n\n

OCR is a technology that converts characters within an image into text, while document parsing analyzes the overall structure, hierarchy, and semantic relationships of a document, converting them into structured data. If OCR focuses on reading what is written, parsing focuses on analyzing how it is arranged structurally. <\/p>\n\n<\/div>\n<\/div>\n

\n

Q3. Why is separate parsing necessary for AI to read documents? <\/strong><\/h3>\n
\n\n

AI can process context more stably with data that maintains paragraph hierarchy, table structure, and positional relationships, rather than plain text. If documents are input via simple copy-pasting, table structures can break, and image context information may be lost. Document parsing is a preprocessing step that converts documents into a format AI can utilize while preserving this structural information. <\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

<\/div>\n\n
<\/div>\n\n
\"Image<\/a><\/figure>\n\n
<\/div>\n\n

In the VLM Era, Document Data Quality Determines AI Performance<\/strong><\/h2>\n\n
<\/div>\n\n

\ud83d\udda5\ufe0f Hancom Data Loader<\/strong><\/a><\/h3>\n\n

As VLM and multimodal AI advance, the quality of input data becomes the practical limit of AI performance. A preprocessing pipeline that supplies accurate data is paramount, even more so than a high-performance model. <\/p>\n\n

Hancom Data Loader structures HWP, HWPX, PDF, and OOXML to create high-quality data that can be integrated into RAG pipelines. Begin with Hancom Data Loader for reliable document preprocessing that agents can trust. <\/p>\n\n

\ud83d\udc49 <\/strong>Go to Hancom Data Loader Live Demo<\/strong><\/a> <\/strong><\/p>\n\n

\ud83d\udc49<\/strong>Explore Hancom Data Loader<\/strong><\/a><\/p>\n\n

\n\n

References<\/strong><\/h2>\n\n
    \n
  1. NVIDIA<\/a>, “What Are Vision Language Models”<\/li>\n\n\n\n
  2. IBM<\/a>, “What are vision language models?”<\/li>\n\n\n\n
  3. Encord<\/a>, “Guide to Vision-Language Models”<\/li>\n\n\n\n
  4. Hancom Tech Blog<\/a>, “Multimodal VLM Technology Trends”<\/li>\n\n\n\n
  5. Parseur<\/a>, “What is OCR (Optical Character Recognition)?”<\/li>\n<\/ol>\n\n

    <\/p>\n","protected":false},"excerpt":{"rendered":"

    This article provides a clear overview of VLM (Vision Language Model), covering its definition, structure, differences from OCR and LLM, and its connection to Document AI data preprocessing. It simplifies the impact of multimodal AI on document pipelines. <\/p>\n","protected":false},"author":2,"featured_media":466,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-465","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ax-glossary"],"_links":{"self":[{"href":"https:\/\/blog.hancom.com\/en\/wp-json\/wp\/v2\/posts\/465","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.hancom.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.hancom.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.hancom.com\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.hancom.com\/en\/wp-json\/wp\/v2\/comments?post=465"}],"version-history":[{"count":15,"href":"https:\/\/blog.hancom.com\/en\/wp-json\/wp\/v2\/posts\/465\/revisions"}],"predecessor-version":[{"id":911,"href":"https:\/\/blog.hancom.com\/en\/wp-json\/wp\/v2\/posts\/465\/revisions\/911"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.hancom.com\/en\/wp-json\/wp\/v2\/media\/466"}],"wp:attachment":[{"href":"https:\/\/blog.hancom.com\/en\/wp-json\/wp\/v2\/media?parent=465"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.hancom.com\/en\/wp-json\/wp\/v2\/categories?post=465"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.hancom.com\/en\/wp-json\/wp\/v2\/tags?post=465"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}