Illustrator forgets to undo the document color mode switch
Here’s a simple test.
1. Create and RGB-based document — the title says 'RGB'
2. Draw something
3. Change the color mode of the document into CMYK — the tab’s title changes accordingly (notice the History displays the generic 'Undo' instead of expected 'Document color mode CMYK')
4. Draw something else again
5. Start undoing steps, either with Cmd/Ctrl+Z or with the History panel. When you reach up the first object drawn, the tab’s title should display RGB — but it still says CMYK! ...and if you hover over the title, the hint appears saying it’s RGB (or not!) ...and if you draw something after this, it stays CMYK now. Ai forgets the document was an RGB one and never undoes it!
If I try this in an older version, without History in it, like CC2017 — it works as expected.
-
hamko1114
commented
Why is that? In my environment, Undo worked correctly in all cases.
I can't determine the cause...
* macOS Sequoia 15.7.7
* Tested with the 2025 release version (29.8.7), 2026 release version (30.3), 2026 public beta (30.7), and 2026 pre-release (30.6); all produced the same result.
* The result is the same whether converting RGB → CMYK or CMYK → RGB.
* In every version, the History panel records the action as "Document Color Mode Conversion."
* Whether using Command+Z or Undo from the History panel, the color mode reverts as expected.----
なぜか私の環境ではいずれも正しくundoできました。
原因がわかりませんね…- Mac OS Sequoia 15.7.7
- 製品版2025(29.8.7)、製品版2026(30.3)、パブリックベータ2026(30.7)、プレリリース2026(30.6)で確認してすべて同じ結果
- RGB→CMYK、CMYK→RGB、どちらに変換しても同じ結果
- どのバージョンでもヒストリーパネルには「ドキュメントカラー変換」として履歴が残る
- Command+Z、ヒストリーパネルどちらでundoしても、意図通りにカラーモードが戻る -
Works fine for me in Beta 30.7.0.11 on Windows 10. The step is just called 'Undo', but it’s possible.
-
monokano
commented
2025 (29.8.7)
Changing the document color mode can be undone correctly using Undo.2026 (30.5.1)
2026 (Beta) (30.6.0 #75)
Changing the document color mode cannot be undone. The Undo command does not restore the previous color mode. -
ajabon grinsmith commented
I noticed this phenomenon in my own work now, and if I searched before posting, it would be a fairly old report. Why hasn't it been fixed yet?