| Version | Change log |
| Blue Iris 6.0.1.13 Jan 7, 2026 |
Fixed: Additional fortifying of decoder and network stability vulnerabilities in low-resource situations or hardware driver deadlock Added: H.265 for the RTSP server, including direct-to-wire capability “Nothing found” messages missing from AI inspector: Continued work to bring stability when camera streaming or decoding fail under rare circumstances. The previous “FORCE quitting” of threads was highly problematic for stability and alternative measures are now used. Network sockets are now handled in a more robust fashion to allow for better recovery in “hung” situations. |
| Blue Iris 6.0.1.12 Jan 6, 2026 |
Fixed: Additional fortifying of decoder and network stability vulnerabilities in low-resource situations or hardware driver deadlock Added: H.265 for the RTSP server, including direct-to-wire capability “Nothing found” messages missing from AI inspector: Continued work to bring stability when camera streaming or decoding fail under rare circumstances. The previous “FORCE quitting” of threads was highly problematic for stability and alternative measures are now used. Network sockets are now handled in a more robust fashion to allow for better recovery in “hung” situations. |
| Blue Iris 6.0.1.11 Jan 6, 2026 |
Fixed: Addressed font issues once again When using the “clipstats” JSON command for an alert, it would return the same record locator as was passed, breaking the ALERT_DB macro if sent to UI3. When using Plate Recognizer for ALPR, the built-in AI OCR is no longer used. Previously, existing plate characters would prevent a call to PR. Objects were rejected as static even when the option to do so was not enabled for alert confirmation. That option will soon be combined with the “require motion” option to simplify things. Deletion of clips from UI3 may have inoperable if the clip was recently previewed Changed: Now using ipv4.icanhazip.com to fetch your IP4 using the Refresh button on Settings/Webserver. The previous connection to the Blue Iris server would return an IPv6 address if you connected that way, and not all routers support that for remote access. Added: If errors are “caught” when using the built-in AI, they are now logged. As a result of and error, the analyzer instance may be reinitialized as well, adding some delay. Some users are finding the need to lower the number of simultaneous analyses from the previous maximum value of 32 down to something more reasonable, perhaps 8 or 4, or even 2. Each instance can use significant RAM and graphics memory, which not all systems can accommodate |
| Blue Iris 6.0.1.10 Jan 6, 2026 |
Fixed: Addressed font issues once again When using the “clipstats” JSON command for an alert, it would return the same record locator as was passed, breaking the ALERT_DB macro if sent to UI3. When using Plate Recognizer for ALPR, the built-in AI OCR is no longer used. Previously, existing plate characters would prevent a call to PR. Objects were rejected as static even when the option to do so was not enabled for alert confirmation. That option will soon be combined with the “require motion” option to simplify things. Deletion of clips from UI3 may have inoperable if the clip was recently previewed Changed: Now using ipv4.icanhazip.com to fetch your IP4 using the Refresh button on Settings/Webserver. The previous connection to the Blue Iris server would return an IPv6 address if you connected that way, and not all routers support that for remote access. Added: If errors are “caught” when using the built-in AI, they are now logged. As a result of and error, the analyzer instance may be reinitialized as well, adding some delay. Some users are finding the need to lower the number of simultaneous analyses from the previous maximum value of 32 down to something more reasonable, perhaps 8 or 4, or even 2. Each instance can use significant RAM and graphics memory, which not all systems can accommodate |
| Blue Iris 6.0.1.9 Jan 3, 2026 |
Fixed: Addressed font issues once again When using the “clipstats” JSON command for an alert, it would return the same record locator as was passed, breaking the ALERT_DB macro if sent to UI3. When using Plate Recognizer for ALPR, the built-in AI OCR is no longer used. Previously, existing plate characters would prevent a call to PR. Objects were rejected as static even when the option to do so was not enabled for alert confirmation. That option will soon be combined with the “require motion” option to simplify things. Deletion of clips from UI3 may have inoperable if the clip was recently previewed Changed: Now using ipv4.icanhazip.com to fetch your IP4 using the Refresh button on Settings/Webserver. The previous connection to the Blue Iris server would return an IPv6 address if you connected that way, and not all routers support that for remote access. Added: If errors are “caught” when using the built-in AI, they are now logged. As a result of and error, the analyzer instance may be reinitialized as well, adding some delay. Some users are finding the need to lower the number of simultaneous analyses from the previous maximum value of 32 down to something more reasonable, perhaps 8 or 4, or even 2. Each instance can use significant RAM and graphics memory, which not all systems can accommodate |
| Blue Iris 6.0.1.8 Dec 30, 2025 |
Fixed: Joystick enumeration and acquisition was non-functional An issue where when hardware video decoding became non-functional (perhaps due to system resources or use by other software such as games, 3D design), cameras may enter a state where they are endlessly in a triggered state and the decoder begins to consume memory. This should now be recognized as a “no signal” state, the trigger should end properly and the stream restarted. A bug where the clip right-click menu to Move items between folders was operating on the wrong items. Changed: Continued improvement to the viewer Find/Find-next function Record locators passed to UI3 are now in a format which survives DB compact and repair operations. |
| Blue Iris 6.0.1.7 Dec 25, 2025 |
Fixed: Issues with Find in Clips in the Viewer with regard to AI Changed: Improved Find in Clips to be more useful. You may now choose to simply search for objects regardless of motion settings, or use them together. Added: A new “Find Next” command to search forward without reopening the Find in Clips dialog. Control-click the search icon, or add a keyboard shortcut (F3 for example) |
| Blue Iris 6.0.1.6 Dec 24, 2025 |
Fixed: Issues with Find in Clips in the Viewer with regard to AI Changed: Improved Find in Clips to be more useful. You may now choose to simply search for objects regardless of motion settings, or use them together. Added: A new “Find Next” command to search forward without reopening the Find in Clips dialog. Control-click the search icon, or add a keyboard shortcut (F3 for example) |
| Blue Iris 6.0.1.5 Dec 23, 2025 |
Fixed: Issues with Find in Clips in the Viewer with regard to AI Changed: Improved Find in Clips to be more useful. You may now choose to simply search for objects regardless of motion settings, or use them together. Added: A new “Find Next” command to search forward without reopening the Find in Clips dialog. Control-click the search icon, or add a keyboard shortcut (F3 for example) |
| Blue Iris 6.0.1.4 Dec 21, 2025 |
Optional built-in AI processing using YOLOv8 ONNX models. Optional face recognition when humans are detected and license plate OCR when vehicles are detected. Registry location for all AI settings moved from OptionsAI to AI The default faces and plates folders are now C:Blue IrisAIfaces and plates Edit the coco.names files in C:BlueIrisAImodels to localize object names. A hyphen is used before the name to ignore specific objects completely to prevent useless clutter. An option on the clips view right-click Move menu to move to Known Faces. This is a convenient way to use a camera to take portraits of family members or automatically saved unknown faces and move them into the Known Faces folder. Visit Settings/AI/Faces in order to sync the face database and OK to restart the AI. DB repair will tolerate manual movement of files between recording folders without losing DB metadata |
