Do not assume cloud synchronization can merge two offline edits to an artwork file. Keep both versions, identify their actual changes and integrate the required work in a separate master. A later timestamp can identify a save event; it does not demonstrate that the other editor's changes survived.
Preserve the branches before choosing a winner
Dropbox explains conflicted copies as a possible result of overlapping edits, including offline editing while another person changes the same file. This is file-synchronization behavior. It is not an application-level promise to combine a background treatment, a text edit and a layer mask into one coherent document.
For a fictional event poster, one editor changes the artwork's background offline while another corrects the date in their own copy. Both edits can be valuable. Renaming the newest file final and deleting the other branch risks losing either the approved background or the correct date.
Compare changes, not only filenames
Make a small table with three columns: baseline, editor A and editor B. Record the background, exact event wording and any other material differences. Open copies rather than overwriting the working files during comparison. A conflicted-copy name is a clue about the synchronization event, not an assessment of which design is correct.
Create an integration copy from an appropriate baseline and bring in the required changes with the editing application's supported operations. Where the edits affect the same object, ask the responsible reviewer to choose a result. Do not silently accept both when they conflict, and do not rely on a flattened preview to reconstruct editable parts that were never supplied.
Copyable integration brief
Preserve baseline, branch A and branch B unchanged. Integrate A's approved background and B's verified event date into a new working master. List any conflicting edits for review. Reopen that master and its exported proof, check both requested changes, then identify the single file designated for the next editing round. Retain the branches until acceptance.
This is a proposed production workflow, not a completed Dropbox or image-editor experiment. Imagild's image outputs can be ingredients in the layout, but this guide does not imply shared-document coediting, conflict merging or file locking inside Imagild.
Prevent another ambiguous round
Agree who owns the next revision before editing resumes. A manual check-out note can be sufficient when the tools do not provide suitable coordination. Work on deliberate branch filenames when simultaneous edits are required, and name the person responsible for integration. Merely waiting for a sync icon does not resolve two incompatible creative decisions.
Accept the consolidated master only after opening the saved file and checking each intended change in context. Confirm the date is correct, the selected background is present and no unrelated layer disappeared. Communicate the new master explicitly to every editor. Keep an ordinary backup as well: a resolved conflict and a recoverable archive answer different questions, and neither should depend on deleting the only copy of a useful branch.