Bonus: Top up now and we'll double your first deposit — get x2 credits instantly.

InternVL3 78B: Self-Hosting & Deployment Guide

InternVL3 78B is the current generation of the InternVL open-weight vision-language family.

What is InternVL3 78B?

InternVL3 78B is the current generation of the InternVL open-weight vision-language family, published by OpenGVLab with open weights at OpenGVLab/InternVL3-78B. LLM API does not route this model today, so there is no endpoint or code sample for it here. What this page does give you is the self-hosting picture: published weight sizes, the VRAM each quantisation needs and the commands to serve it yourself. Every figure is read from the public repository and refreshed weekly.

How to run InternVL3 78B yourself

Open weights (other), 78.4B parameters. Below: how much memory the weights need at each quantization, which hardware fits them, and the commands to serve it.

InternVL3 78B VRAM requirements

Precision / quantizationWeightsFigureSource
BF16 (full precision)156.8 GBEstimate78.4B params × 2 bytes
FP886.6 GBFile sizebrandonbeiler/InternVL3-78B-FP8-Dynamic
AWQ 4-bit52.9 GBFile sizeOpenGVLab/InternVL3-78B-AWQ
MLX 4-bit52.1 GBFile sizemlx-community/InternVL3-78B-4bit
GGUF Q4_K_M47.4 GBFile sizeunsloth/InternVL3-78B-Instruct-GGUF
GGUF Q2_K29.8 GBFile sizeunsloth/InternVL3-78B-Instruct-GGUF

File size = actual download size on Hugging Face. Estimate = parameter count × bytes per weight. Weights only — the KV cache for long contexts needs extra memory; the fit tables below add 15% headroom as a rule of thumb.

GPU requirements: deploy InternVL3 78B on your hardware

HardwareBF16 (full precision)FP8AWQ 4-bitMLX 4-bitGGUF Q4_K_MGGUF Q2_K
NVIDIA H200141 GB
NVIDIA H10080 GB
NVIDIA A100 80GB80 GB
NVIDIA L40S48 GB

GPUs needed per variant.

HardwareGGUF Q4_K_MGGUF Q2_K
RTX 509032 GB
RTX 409024 GB
RTX 309024 GB

GGUF via llama.cpp; more cards or CPU offload for larger files.

HardwareGGUF Q4_K_MGGUF Q2_KMLX 4-bit
Mac, 512 GBM3 UltraFitsFitsFits
Mac, 192 GBM2 UltraFitsFitsFits
Mac, 128 GBM4 Max / M3 MaxFitsFitsFits
Mac, 64 GBM4 Pro / MaxFits

Assumes ~75% of unified memory is usable by the GPU.

HardwareBF16 (full precision)FP8AWQ 4-bitMLX 4-bitGGUF Q4_K_MGGUF Q2_K
AWS p5.48xlarge8× H100 · 640 GBFitsFitsFitsFitsFitsFits
AWS p4de.24xlarge8× A100 80GB · 640 GBFitsFitsFitsFitsFitsFits
AWS g6e.12xlarge4× L40S · 192 GBFitsFitsFitsFitsFitsFits
Google Cloud a3-highgpu-8g8× H100 · 640 GBFitsFitsFitsFitsFitsFits
Azure ND H100 v58× H100 · 640 GBFitsFitsFitsFitsFitsFits

Whole-instance GPU memory; public instance specs.

Serve it yourself

pip install -U vllm
vllm serve OpenGVLab/InternVL3-78B
pip install 'sglang[all]'
python -m sglang.launch_server --model-path OpenGVLab/InternVL3-78B
llama-server -hf unsloth/InternVL3-78B-Instruct-GGUF:Q4_K_M \
  --ctx-size 32768 --n-gpu-layers 99
pip install -U mlx-lm
mlx_lm.generate --model mlx-community/InternVL3-78B-4bit --prompt "Hello"

Commands use the official repositories above; vLLM and SGLang expose an OpenAI-compatible endpoint.

Not on LLM.API yet

We do not route this model through our API at the moment. Browse the models you can call today — most workloads have a close match already live.

Not available on LLM API yet

We do not route this model through our API at the moment, so there is no endpoint or code snippet for it yet. Browse the models you can call today — most workloads have a close match already live.

Browse available models

Why run InternVL3 78B on LLM.API?

  • Unified AI Routing

    Reach InternVL3 78B and sibling models through one OpenAI-compatible endpoint.

  • Cost Control

    Production: Compare provider price points and keep spend visible as you scale InternVL3 78B.

  • Reliability Layer

    Retry and route across configured providers when a single upstream blips.

  • Observability

    Trace prompts, tokens, and errors for InternVL3 78B alongside the rest of your stack.

  • Drop-in SDKs

    Keep using familiar OpenAI client patterns with base URL https://api.llmapi.ai/v1.

  • Model Breadth

    Swap InternVL3 78B for chat, media, or embedding alternatives without rewriting auth.

When to Use — When NOT to Use

Get one key to every model

Swap your API key. Keep your code.