MSVC installer
PineconeMC-Windows-MSVC-Setup-11.0.3.exe
Download fileOfficial release assets
Use this ElyPrismLauncher download page to choose the PineconeMC installer or portable build that matches your operating system and architecture. The current release listed here is 11.0.3.
Windows
MSVC is the usual choice for a modern Windows installation. Use a portable ZIP when you want to keep the launcher in a self-contained folder.
PineconeMC-Windows-MSVC-Setup-11.0.3.exe
Download filePineconeMC-Windows-MSVC-Portable-11.0.3.zip
Download filePineconeMC-Windows-MSVC-arm64-Setup-11.0.3.exe
Download filePineconeMC-Windows-MSVC-arm64-Portable-11.0.3.zip
Download filePineconeMC-Windows-MinGW-w64-Setup-11.0.3.exe
Download filePineconeMC-Windows-MinGW-arm64-Setup-11.0.3.exe
Download filemacOS
The current macOS assets are published for Intel and Apple silicon systems. Start with the DMG unless you specifically need the archive.
PineconeMC-macOS-11.0.3.dmg
Download filePineconeMC-macOS-11.0.3.zip
Download fileLinux
AppImage is the easiest starting point for many Linux users. The portable archive is useful when you prefer to manage the extracted folder yourself.
PineconeMC-Linux-x86_64.AppImage
Download filePineconeMC-Linux-Qt6-Portable-11.0.3.tar.gz
Download filePineconeMC-Linux-aarch64.AppImage
Download filePineconeMC-Linux-aarch64-Qt6-Portable-11.0.3.tar.gz
Download filePineconeMC-ArchLinux-11.0.3.pkg.tar.zst
Download fileWhich file should I choose?
You want the normal Windows or macOS setup flow, shortcuts and an application installed in the usual location.
You want to keep the launcher folder on another drive, carry it between environments or avoid a traditional installation step.
x64 is common on Intel and AMD Windows/Linux systems. ARM64 is for compatible ARM hardware. On macOS, use the published universal asset and let macOS handle the application.
Why there are several files
A PineconeMC release is published for different operating systems, CPU architectures and installation preferences. The file that is right for a Windows x64 desktop is not automatically right for Windows ARM64, Linux aarch64 or macOS. Portable archives also solve a different problem from installers: they let you keep the launcher folder together, but they may require you to manage shortcuts, permissions and updates yourself.
This page keeps the ordinary end-user builds together and leaves source archives and update-helper files on the official release page. That makes the download choice easier to scan without hiding the complete release. If you are following a developer build instruction, need a zsync file or want to inspect source code, open the release page and confirm that the asset matches the instruction before downloading it.
A final source check
Before opening an ElyPrismLauncher download, compare the current release tag, filename, operating system, architecture and file format. The Windows x64 installer is a normal starting point for most Intel and AMD PCs, while ARM64, macOS and Linux assets serve different devices. Portable files solve a folder-management need; they are not automatically safer or newer.
Each ElyPrismLauncher download listed here is tied to the PineconeMC release metadata and the official GitHub destination. If a redirect lands somewhere unexpected, the filename changes, or a browser warning names a different publisher, stop and open the official release page directly. Do not replace a missing asset with a random mirror, cracked repack or extra executable.
After an ElyPrismLauncher download succeeds, follow the installation guide and create a small vanilla instance. Keep the release tag and asset name with your backup so an older modpack can be restored without guessing which build was used. The download page is for choosing a platform file; the troubleshooting and version pages explain what to do when the launcher or metadata service behaves differently.
Before you open a file
A release page and a local file should describe the same PineconeMC build. These checks help you catch a wrong architecture, a stale link or an unexpected repack before you open an ElyPrismLauncher download.
Compare the version in the filename with the release tag shown above and on the official GitHub page. Do not rename an older file and treat it as a newer build.
Use Windows, macOS or Linux assets for the operating system you are running. Then check x64, ARM64, x86_64 or aarch64 before launching the file.
Installers are executable files, portable builds are archives, AppImage files are Linux applications and DMG files are macOS disk images. A download page should not ask you to run an unrelated helper.
The release data on this site records the official source URL, filename, platform, architecture, format and published size for each installable or runnable build shown here. The URLs were checked through GitHub's redirect with a small byte-range request and matching binary signature on 2026-08-14. That confirms the published address responds as the expected kind of file; it is not a substitute for your own antivirus review, a full checksum comparison or checking the file after a future release update.
If the filename, size, release tag or platform does not match, stop and open the official release page directly. Avoid unknown mirrors, cracked repacks and installers that bundle extra software.
Download questions
PineconeMC is the current project name used by the launcher formerly known as ElyPrismLauncher. This site keeps the old name in titles and explanations so existing searches remain understandable.
For most users, choose the Windows x64 MSVC installer. Use ARM64 only when your Windows device uses ARM hardware. Choose portable if you do not want a traditional installation.
Use the official Release history for older builds. The versions page explains why old files should be matched to a specific Minecraft instance and why unsupported mirrors are not listed.
Do not dismiss a warning automatically. Confirm the source URL, filename, release tag and file metadata, then compare the result with the official release discussion or issue tracker. Read the safety guide for a cautious workflow.
Follow the installation guide, then add an account and create a test instance before importing large modpacks.