LayoutLMv3 Base is a multimodal Transformer model developed by Microsoft, capable of handling both text and image inputs for tasks such as document understanding and visual question answering. It is genuinely best at general-purpose pre-trained tasks, including form and receipt understanding, as well as document image classification and layout analysis.
Input
Output
Context
1K
Max Output
1K
Parameters
125.3M
Input Modalities
Output Modalities
Loading capabilities…
Estimates based on INT8 quantization at up to 32K context. A count above one assumes tensor parallelism across the cards. Actual requirements vary by framework and configuration.
The creator's other models in the catalog, with their context, size and license where published.
Put this model beside its alternatives on the same evidence, or go back to the full catalog.
Answered from the entry's own fields: context, license, modalities, evidence, serving and the memory to self-host.
Layoutlmv 3 Base advertises a context window of 514 tokens, with a maximum output of 512 tokens in a single response. The figure is the creator's published maximum; a given host may serve less, and the gateway routes on what each host actually serves.
Yes. Layoutlmv 3 Base is an open-weight model released under the Cc by nc sa 4.0 license, so the weights can be downloaded and self-hosted within that license's terms.
Layoutlmv 3 Base accepts Text and Image and produces Text. The capabilities card on this page lists which API features each deployment honours, such as function calling and structured output, with the source each was checked against.
No published benchmark result for Layoutlmv 3 Base is in the catalog yet, so the model is shown as unmeasured. It is not ranked or estimated; the router treats it as unknown for every task until a suite measures it.
Not on the managed pool today; Layoutlmv 3 Base is listed for reference and comparison. Connect your own provider key or endpoint that serves it and the gateway runs it on your account, with routing decisions recorded the same way.
About 0.5 GB at INT8 for the weights and a default context, from the catalog's 125.3M parameter count; FP16 needs roughly twice that, and long contexts or many concurrent requests add KV cache on top. The GPU section on this page lists cards that hold it, and the capacity planner sizes it for your context length and traffic.
Fields collected from public registries, host APIs and benchmark publishers, each tagged with its source.
Last updated: Aug 28, 2026
One gateway in front of every model, with your policies applied and every decision on record. Start with $5 of credit and 5,000 routing decisions a month, no card required.