2025-07-10 16:02:40 +01:00
---
toc_depth: 3
---
2025-07-08 11:27:40 +01:00
# Engine Arguments
2025-05-23 11:09:53 +02:00
Engine arguments control the behavior of the vLLM engine.
2025-07-08 10:49:13 +01:00
- For [offline inference ](../serving/offline_inference.md ), they are part of the arguments to [LLM][vllm.LLM] class.
- For [online serving ](../serving/openai_compatible_server.md ), they are part of the arguments to `vllm serve` .
2025-05-23 11:09:53 +02:00
2025-07-10 16:02:40 +01:00
The engine argument classes, [EngineArgs][vllm.engine.arg_utils.EngineArgs] and [AsyncEngineArgs][vllm.engine.arg_utils.AsyncEngineArgs], are a combination of the configuration classes defined in [vllm.config][]. Therefore, if you are interested in developer documentation, we recommend looking at these configuration classes as they are the source of truth for types, defaults and docstrings.
2025-08-09 16:31:32 +01:00
When passing JSON CLI arguments, the following sets of arguments are equivalent:
- `--json-arg '{"key1": "value1", "key2": {"key3": "value2"}}'`
- `--json-arg.key1 value1 --json-arg.key2.key3 value2`
Additionally, list elements can be passed individually using `+` :
- `--json-arg '{"key4": ["value3", "value4", "value5"]}'`
- `--json-arg.key4+ value3 --json-arg.key4+='value4,value5'`
2025-07-10 16:02:40 +01:00
## `EngineArgs`
2025-05-23 11:09:53 +02:00
2025-07-10 16:02:40 +01:00
--8<-- "docs/argparse/engine_args.md"
2025-05-23 11:09:53 +02:00
2025-07-10 16:02:40 +01:00
## `AsyncEngineArgs`
2025-05-23 11:09:53 +02:00
2025-07-10 16:02:40 +01:00
--8<-- "docs/argparse/async_engine_args.md"