Except rendering, most calculations are performed on CPU, therefore having a faster GPU will generally not impact the overall speed of the application. GPU texture memory (VRAM) should be larger than your largest dataset (e.g., working with 2GB data, get VRAM > 4GB) and check that your images fit in maximum texture dimensions of your GPU hardware. Discrete graphics card (such as NVidia GPU) is recommended for interactive 3D volume rendering and fast rendering of complex scenes. Integrated graphics card is sufficient for basic visualization. GPU: Graphics must support minimum OpenGL 3.2. Graphics: Dedicated graphics hardware (discrete GPU) memory is recommended for fast volume rendering. As a general rule, have 10x more memory than the amount of data that you load.ĭisplay: a minimum resolution of 1024 by 768 (1280 by 1024 or better is recommended). Memory: more than 4GB (8 or more is recommended). Latest LTS (Long-term-support) version is recommended. Latest public release is recommended.ĬentOS 7 or later. MacOS: macOS Big Sur (11) or later (both Intel and ARM based systems). Microsoft does not support Windows 8.1 and Windows 7 anymore and Slicer is not tested on these legacy operating system versions, but may still work. Windows 10 Version 1903 (May 2019 Update) version or later is required for support of international characters (UTF-8) in filenames and text. Windows: Windows 10 or 11, with all recommended updates installed. For example, 3D Slicer + Jupyter notebook in a web browser is available for free via Binder service (no installation needed, the application can run in any web browser). Slicer can also run on virtual machines and docker containers. Older computers may work (depending mainly on graphics capabilities). System requirements ģD Slicer runs on any Windows, Mac, or Linux computer that was released in the last 5 years. This page contains information that you need to get started with 3D Slicer, including how to install and use basic features and where to find more information. for early versions of Fiji, and other miscellany.Welcome to the 3D Slicer community.Just prior to extensive changes reconciling Fiji with ImageJ2.

Just prior to some big changes to ImageJ2 under the hood. Just prior to a big update to facilitate reproducible builds. Just prior to starting the transition to Java 8. The final version of Fiji using Java 6, for all platforms. Here are Life-Line versions from before Fiji switched to Java 8. Just prior to a sweeping update to nearly all components. Here are Life-Line versions of Fiji created after the switch to Java 8. The idea is that if something goes horribly wrong, you can fall back to a stable version. This sections offers older downloads of Fiji, preserved just prior to introducing major changes. You can download previous Fiji builds by date stamp from the archive. See the source code page for details on obtaining the Fiji source code.

If you encounter bugs, please see the Getting Help page.

Many common questions are answered on the FAQ.

That means that you do not have to run an installer just download, unpack and Support for installing Fiji via Flatpak is in the works see Alternatively you can install the no-JRE version which defaults to the Mac Java and will limit some native library functionality that does not yet have Arm64 support ().

MacOS Arm64 Note: The default MacOS download should run on Arm64 via the Rosetta translator ((software)) which may come at some performance cost.

However, Fiji (like ImageJ) should run on any system for which a Java 8 runtime is available (Solaris, Raspbian, etc.). Fiji is supported on the following systems:

Bit slicer on mac