PyInstaller one-file versus one-folder on Windows

Scope

This comparison covers the two PyInstaller bundle layouts for Windows 11 x64. It records what the local release estate exercises. It does not compare every bootloader, antivirus, or application-startup condition.

Answer

For the estate’s PolyForm Noncommercial/Internal Use distributions, use --onedir because bundled LGPL Qt and other LGPL libraries must remain replaceable by end users. This is the mapped estate decision rule, not a general preference for --onedir.

--onefile was not chosen or reproduced for that mapped PolyForm route. The canonical SXT policy permits either layout for MIT/open-source tools, where source is available for rebuilding and relinking. This does not remove dependency notices or other obligations, and it does not make either layout universally correct.

Need	`--onedir`	`--onefile`
Mapped PolyForm LGPL-replaceability evidence	Yes	No
Portable ZIP input	Full output folder	Viable but not reproduced here
Shared Inno installer input	Full output folder	Viable but not reproduced here
Present local app release route	Yes	No

Decision path

Determine whether dependency licensing requires end users to replace or relink bundled libraries. If that requirement applies, choose the mapped --onedir route.
Include the complete output folder in the ZIP. Do not distribute only the .exe unless your own build proves it is sufficient.
Point the installer at the --onedir output folder when using the shared workflow for that PolyForm route.
For an MIT/open-source SXT, either layout is available under the canonical policy. Apply the actual dependency obligations, then test the released artifact, asset behavior, update approach, and installer integration.

Production evidence

Simple UNA Log Viewer’s build script invokes pyinstaller --onedir and collects PySide6 and qtpy. The shared release workflow compresses the complete distribution folder and passes that folder to Inno Setup.

Unsupported or external outcomes

--onefile was not chosen or reproduced for the mapped PolyForm route.
The evidence is pywebview plus PySide6 Qt backend, not a standalone native PySide6 app.
Authenticode signing, Store or MSIX, and general WinGet acceptance are external outcomes.
Hashes and provenance can document bytes and build origin, but neither establishes malware safety or SmartScreen reputation.
This is not legal advice. Layout alone does not fulfill all license obligations; notices, source or offer requirements, and the actual dependency and license versions still matter.

Source ledger