Download and install YSFlight on Windows, macOS or Linux, with clear ZIP extraction steps and fixes for launch, graphics and permission errors.
Download YSFlight from the simulator’s official release page, choose the package for your operating system, extract it to a normal writable folder, and launch the included program. On Windows, YSFlight is commonly distributed as a ZIP rather than a conventional installer, so do not run it from inside the archive.
YSFlight is freeware, so you should not need a paid installer or third-party download manager. If you are still deciding whether it suits your computer, see where YSFlight fits among free PC flight simulators.
Which YSFlight download should I choose?
Choose a pre-built package matching your operating system and processor; source-code packages are only for people who intend to compile the simulator themselves.
| Package | Choose it when | What to expect |
|---|---|---|
| Windows | You use a Windows PC | Usually a ZIP archive or, for some releases, a setup program. |
| macOS | The listed build supports your macOS version and processor | An application bundle, disk image or compressed archive. Older builds may not run on newer macOS releases. |
| Linux | The package matches your processor architecture and required libraries | A compressed folder containing the executable and supporting data. |
| Source code | You plan to build YSFlight yourself | Not a ready-to-run simulator and unnecessary for a normal installation. |
If several graphics builds are offered, start with the one recommended in the accompanying release notes. An alternative renderer is useful when the normal build opens to a black screen or closes during start-up.
How do I install YSFlight on Windows?
A Windows ZIP release is a portable installation: extraction installs it, and the complete extracted folder must remain together.
- Download the official Windows package. Save it somewhere easy to find, such as
Downloads. Avoid repackaged installers and pages that require their own download manager. - Check the archive. Scan it with your installed security software and compare its checksum if the official release page provides one.
- Extract every file. Right-click the ZIP, select the Windows extraction option, and choose a destination. Our Windows archive extraction walkthrough covers this process and the common nested-folder mistake.
- Use a writable location. A folder such as
Documents\YSFlightis suitable for a portable build. Avoid placing it manually insideProgram Files, where older applications can encounter permission problems. If the download contains a proper installer, its proposed location is normally fine. - Keep the extracted structure intact. Do not copy only the executable to the desktop. YSFlight needs the aircraft, scenery and other data folders stored beside it.
- Launch the supplied YSFlight program. Open the extracted folder and run the executable whose name identifies it as YSFlight. If the package includes a setup program instead, run that and follow its prompts.
If Windows displays a SmartScreen warning, first confirm that the file came from the official release and that its details match the expected package. Only then use the option to view more information and run it; do not disable security protection system-wide.
How do I install YSFlight on macOS or Linux?
macOS
Extract or mount the downloaded package, then move the complete supplied application or folder to the location recommended by its included instructions.
If macOS says the developer cannot be verified, confirm the download’s origin and use the one-time Control-click and Open method if appropriate. A message saying the application must be updated or is incompatible usually indicates an unsupported older architecture; changing security settings will not repair that incompatibility.
Linux
Extract the complete package and launch YSFlight from that directory so it can find its data files.
If Linux reports Permission denied, mark the supplied launcher as executable through the file properties or with chmod +x. Starting it from a terminal can reveal a missing shared library or architecture mismatch; install dependencies through the operating system’s package manager rather than downloading individual library files from unrelated sources.
Why won’t YSFlight start after extraction?
Most YSFlight start-up failures come from incomplete extraction, a separated executable, blocked file access or an incompatible package.
- No aircraft or scenery appears: extract the archive again and preserve its directory structure. This often happens when only the executable has been moved.
- Settings will not save: move the portable installation to a folder owned by your Windows account, then run it normally rather than relying on administrator mode.
- A missing DLL or shared-library error appears: confirm that you downloaded the correct operating-system and processor build. Do not install loose DLL files from download sites.
- The screen is black or the program closes: try the alternative official graphics build if the package provides one, begin in windowed mode, and update the graphics driver supplied for your hardware.
- Security software removed the executable: verify the source before restoring anything. If verification is uncertain, delete the package and obtain a fresh official copy.
What should I configure before the first flight?
Begin in windowed mode, connect your controller before opening YSFlight, and calibrate its axes in the simulator’s controller settings.
Check that pitch, roll, rudder and throttle move in the correct directions before take-off. If a joystick is not listed, confirm that the operating system can see it, close YSFlight, reconnect the device and start the simulator again. When using multiplayer, allow network access only on the network types you trust; ordinary offline flying does not require a public-network firewall exception.
Can I move or update a portable YSFlight installation?
You can move a portable YSFlight installation while it is closed, but move the entire folder rather than the executable alone.
For an update, extract the new release into a separate folder first and verify that it starts. Copy user-created content only as directed by the release documentation; overwriting an old installation can leave obsolete files mixed with the new package.