QIDI Studio
QIDI Studio 2.4.1.10
Official release record for QIDI Studio 2.4.1.10, published Jan 24, 2026.
Official files in this release
Windows · 2 files
- QIDIStudio_Setup_02.04.01.10_Win64.exeIntel / AMD 64-bit · 276.2 MiB · 4,690 downloadsOfficial download ↗
✓ SHA-256 available
Verify this file
Expected SHA-2566be22c6f4049e5499c73781ce2576456eea08fdb74fab8d80b77b85aee1ce9b3Local verification commands
Windows PowerShellGet-FileHash -Algorithm SHA256 -LiteralPath '.\QIDIStudio_Setup_02.04.01.10_Win64.exe'macOS Terminalshasum -a 256 -- 'QIDIStudio_Setup_02.04.01.10_Win64.exe'Linux terminalsha256sum -- 'QIDIStudio_Setup_02.04.01.10_Win64.exe'The digest is supplied by GitHub for the publisher’s release asset. A matching local result shows that the downloaded bytes match that asset.
SHA-256 verifier → - QIDIStudio_v02.04.01.10_Win64.zipIntel / AMD 64-bit · 279.0 MiB · 575 downloadsOfficial download ↗
✓ SHA-256 available
Verify this file
Expected SHA-256d5ee834d42533061847520e972d28a9a387b0382e9a0794aea0ec8b8dbbfc5b5Local verification commands
Windows PowerShellGet-FileHash -Algorithm SHA256 -LiteralPath '.\QIDIStudio_v02.04.01.10_Win64.zip'macOS Terminalshasum -a 256 -- 'QIDIStudio_v02.04.01.10_Win64.zip'Linux terminalsha256sum -- 'QIDIStudio_v02.04.01.10_Win64.zip'The digest is supplied by GitHub for the publisher’s release asset. A matching local result shows that the downloaded bytes match that asset.
SHA-256 verifier →
macOS · 1 files
- QIDIStudio_v02.04.01.10_MacOS_universal.dmgUniversal · 164.7 MiB · 613 downloadsOfficial download ↗
✓ SHA-256 available
Verify this file
Expected SHA-256396c6dc22554eb5be2c70e806866f06a06b127ef90fcd4b92dc2aec46c75f5bfLocal verification commands
Windows PowerShellGet-FileHash -Algorithm SHA256 -LiteralPath '.\QIDIStudio_v02.04.01.10_MacOS_universal.dmg'macOS Terminalshasum -a 256 -- 'QIDIStudio_v02.04.01.10_MacOS_universal.dmg'Linux terminalsha256sum -- 'QIDIStudio_v02.04.01.10_MacOS_universal.dmg'The digest is supplied by GitHub for the publisher’s release asset. A matching local result shows that the downloaded bytes match that asset.
SHA-256 verifier →
Linux · 2 files
- QIDIStudio_v02.04.01.10_Ubuntu22.AppImageNot specified in filename · 106.6 MiB · 182 downloadsOfficial download ↗
✓ SHA-256 available
Verify this file
Expected SHA-2565081520d8495fbc8b136b0b973d6b13dc0213b3f8d53ea84b7ce455ecf49bdd0Local verification commands
Windows PowerShellGet-FileHash -Algorithm SHA256 -LiteralPath '.\QIDIStudio_v02.04.01.10_Ubuntu22.AppImage'macOS Terminalshasum -a 256 -- 'QIDIStudio_v02.04.01.10_Ubuntu22.AppImage'Linux terminalsha256sum -- 'QIDIStudio_v02.04.01.10_Ubuntu22.AppImage'The digest is supplied by GitHub for the publisher’s release asset. A matching local result shows that the downloaded bytes match that asset.
SHA-256 verifier → - QIDIStudio_v02.04.01.10_Ubuntu24.AppImageNot specified in filename · 108.4 MiB · 435 downloadsOfficial download ↗
✓ SHA-256 available
Verify this file
Expected SHA-25640dbdbf9a188bff1f19b5d27d2280cb889e61cd96d178f0e4a7af83c0d2042efLocal verification commands
Windows PowerShellGet-FileHash -Algorithm SHA256 -LiteralPath '.\QIDIStudio_v02.04.01.10_Ubuntu24.AppImage'macOS Terminalshasum -a 256 -- 'QIDIStudio_v02.04.01.10_Ubuntu24.AppImage'Linux terminalsha256sum -- 'QIDIStudio_v02.04.01.10_Ubuntu24.AppImage'The digest is supplied by GitHub for the publisher’s release asset. A matching local result shows that the downloaded bytes match that asset.
SHA-256 verifier →
Package changes from the previous release
Compared with 2.4.0.70, the number of public application files changes from 4 to 5.
Platform
- Linux1 → 2Added +1
Architecture
- Not specified in filename1 → 2Added +1
Format
- APPIMAGE1 → 2Added +1
Counts are separate views of publisher filenames by platform, processor and format. They are not compatibility or support guarantees.
Release-note preview
A plain-text excerpt from the publisher’s release notes. Open the official release for the complete and current text.
Publisher notes are shown in their original source language. This excerpt is not machine-translated.
QIDIStudio.logo
This is the QIDIStudio v02.04.01.10 version. This is a test version and no updates will be pushed at present.
Bug Fixes
- Fix the bug causing failure in opening non-QIDI 3mf files.
- Fix the bug of incorrect logic for enabling multi-color boxes in the print page sending process: When closing the multi-color printing box, the consumable will automatically be set to "Ext"; when enabling the multi-color printing box, the consumable will automatically be matched. Similarly, when selecting the consumable, if "Ext" is chosen, the button for enabling multi-color printing will automatically be set to "Off"; when selecting the consumable in the box, the button for enabling multi-color printing will automatically be set to "On".。
fix_bug1
- During the synchronization of consumables, an incorrect machine type switch may occur.
Miscellaneous
- Fix the support for Spanish language. (#158)
- Optimize the overall layout of the equipment page.
- Optimize the connection method for the device page (for new machines or for some old machines with firmware support).
- Add an air conditioning on/off switch to the printed page (this requires the machine to support it first).
- Optimize the configuration of the X-Max 4 machine.
Note for Linux Users
On newer versions of Ubuntu (e.g., Ubuntu 24), the software may crash when connecting to a printer on the device page. You can try the following three methods to temporarily work around this issue.
- Configure WEBVIEW before launching the software (Only for Ubuntu 24). — Use the following command to attempt opening the software: — ~~~cmd — WEBKITDISABLECOMPOSITINGMODE=0 WEBKITDISABLEDMABUFRENDERER=0 ./QIDIStudio2.02.01.62Ubuntu24.AppImage — ~~~ — Note: Using the above command to launch the software ensures that the Fluidd page can be opened and print tasks can be sent normally, but it may result in blank home, guide, and login pages.
- If the first method doesn't work, you can manually add port "7125" when adding a device. — The downside of this approach is that Fluidd cannot be opened from the device page, but it ensures the software does not crash after sending or starting a print job.
- If all the above methods fail, you will need to manually export the G-code file, then open the corresponding device's Fluidd in a browser. — In the task list, select "Upload File" and then execute the print operation. See the example below.