If you run combat in DMGrid while a player keeps another character sheet, agree who communicates each change and check both records. The public documentation consulted does not describe synchronization between DMGrid and DnD Dynamic Sheet. You do not have to use both programs: DMGrid also includes character sheets and hit points.
A turn with two records
Imagine a fictional in-person table. The game master uses DMGrid on a Windows PC and a player keeps the same character in DnD Dynamic Sheet on another computer. Before a hit they agree the character has 12 current HP. The table resolves 7 damage with no other adjustment applicable in this example: 5 HP remain.
The game master can reflect 5 HP in the record used to run the game; the player checks 5 on their own sheet. Decide which value will be the reference if the numbers later differ, and reconstruct the change together before continuing. Do not assume editing one screen updates the other: the coordination described here is manual, not an announced integration.
The HP maximum does not rise or fall in this example. If temporary hit points, resistance or another rule applies, resolve your actual case with the table first; do not reuse 5 without checking.
What each tool offers
The DMGrid public product sheet describes a campaign archive, board, pieces, initiative, hit points, character sheets and a separate player display. It is designed for one person running an in-person table on a Windows PC; it does not create multiplayer browser rooms.
The DnD Dynamic Sheet product sheet describes a Windows character sheet with HP, actions, movement, notes and counters. It does not include shared maps or campaign management. If a single sheet in DMGrid is enough for your group, use it; a second application adds another record the table needs to keep current.
Before setting up the session
- Agree who maintains the reference value and when they communicate it, for example after resolving damage or healing.
- If you keep two records, compare the current value after the change; do not change the maximum unless appropriate.
- If the numbers differ, review the prior state and effects applied by the table. One screen alone does not explain which rule was missed.
- Check what Player View displays before showing information to the group. A player display is a local view, not an online room.
Other workflows exist. D&D Beyond Maps describes character sheets and map tokens within its own service; Roll20 Characters describes exporting characters into its games. They are separate ecosystems: check their current terms and do not infer a connection to IliciLabs apps.
DMGrid is a paid Windows beta. Consult its product page for current requirements and terms. The cover is an AI-generated illustrative scene, not a screenshot of the applications.