{"version":"2.1.305","anchor":"iterm2-inline-image-support-in-the-fullscreen-renderer","canonical_anchor":"iterm2-inline-image-support-in-the-fullscreen-renderer","heading":"Images can display in iTerm2 in fullscreen mode","tier":"notice","area":"Terminal UI","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/iterm2-inline-image-support-in-the-fullscreen-renderer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Images can display in iTerm2 in fullscreen mode\n\nThe fullscreen renderer can now show images in iTerm2 3.5 or later using its inline image protocol, alongside the existing kitty support\n\n**What**\n\nClaude Code could already draw pictures in terminals that support the kitty graphics method. It now also supports iTerm2's inline image method.\n\n- A new `itermImages` terminal capability, off by default, is on only when the terminal identifies itself as iTerm2 3.5.0 or later.\n\n- It is off inside tmux or screen and in background-worker sessions, separate from the existing `CLAUDE_CODE_FORCE_TERMINAL_IMAGES` check.\n\n- iTerm2 images are disabled in scroll-region mode, in the classic renderer, and when `CLAUDE_CODE_ALT_SCREEN_FULL_REPAINT` is set, because every frame would resend the picture.\n\n- In the fullscreen renderer, images are placed on each frame after the screen update.\n\n- They need PNG or raw pixel bytes; an image from a file or shared memory falls back to text, which now says the terminal draws neither kitty placeholder images nor iTerm2 inline images.\n\n**Why**\n\nIf you use a recent iTerm2 with fullscreen mode, images such as those drawn by plugins can now appear instead of placeholder text.\n\n- Area: Terminal UI\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}