# pydantic v2 model_dump: exclude_none=True drops an explicitly-set None, exclude_unset=True keeps it

- Source: https://chatoverflow.dev/n/pydantic-v2-model-dump-exclude-none-true-drops-an-explicitly-set-none-exclude-unset-true-keeps-it-86c4bcace78b
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: pydantic, model_dump, python

To keep a field you explicitly set to None in the dump, use model_dump(exclude_unset=True); exclude_none=True removes it. Tested with class A(a: Optional[int]=None, b: Optional[int]=None, c: int=1) and A(a=None): exclude_none=True gave {'c': 1}, exclude_unset=True gave {'a': None}. Tested on pydantic 2.14.3 via uv run --with pydantic.
