Executable File Extensions List
Grab a copy-ready list of executable and installer file extensions across Windows, macOS, Linux, and mobile platforms. Each entry includes the extension and its meaning for fast reference.
Executable file extensions(34 extensions)
Ordered by platform (Windows, macOS, Linux, mobile, cross-platform); includes scripts that are directly executed but excludes library files (.dll, .so, .dylib) and bytecode-only formats.
How to use this list
Copy executable extensions in seconds
Takes ~5 seconds- 1Choose a format
Pick text for docs, JSON for code, or HTML for dropdown menus.
- 2Copy or download
Click the copy button or download the file for offline use.
- 3Paste into your project
Drop the list into a validation rule, file-type filter, documentation page, or UI dropdown.
Who uses this list?
- Developers building file upload validators or security filters that block or allow executable types
- Security engineers and sysadmins documenting or auditing allowed executable formats by platform
- Technical writers creating documentation or reference tables for cross-platform deployment guides
Examples
Text output with extension and meaning.
.exe - Windows Executable
.exe - Windows Executable
JSON output with bare extension values for code.
".exe"
[".exe", ".msi", ".bat", ".app", ".dmg", ".deb", ".rpm", ".apk", ...]
HTML output for a file-type dropdown.
.exe - Windows Executable
<option value=".exe">.exe - Windows Executable</option>
A reference list of executable file extensions
Use this list when you need a reliable, copy-ready set of executable and installer file extensions across all major platforms, each labeled with its purpose.
Looking for a complete executable file extensions list to use in a validator, security rule, or documentation page? This reference covers the most common executable and installer formats across Windows (.exe, .msi, .bat, .cmd, .ps1), macOS (.app, .dmg, .pkg, .command), Linux (.sh, .deb, .rpm, .run, .AppImage, .snap, .flatpak), mobile (.apk, .aab, .ipa), and cross-platform runtimes (.jar, .py, .js). Each entry uses a clear label pairing the extension with its meaning, while the JSON output emits only the bare extension strings — perfect for file-type whitelists, blocklists, and upload validators. The HTML format generates ready-to-paste option tags for select menus in admin panels or configuration UIs. Developers building security tools and sysadmins documenting platform policies will find this list especially useful as a consistent, deterministic starting point. Because the dataset is scoped to files that are directly executed or launched by the operating system, it intentionally excludes shared libraries (.dll, .so, .dylib) and compiled bytecode files that are not themselves executable entry points.
Covers executable and installer formats for Windows, macOS, Linux, Android, and iOS.
- Windows: .exe, .msi, .bat
- macOS: .app, .dmg, .pkg
- Linux: .deb, .rpm, .AppImage
Each entry pairs a human-readable description with the bare file extension for clean reuse.
- Descriptive labels
- Bare extension as value
- JSON outputs extensions only
Switch between text, JSON, and HTML formats to fit any workflow.
- Plain text for docs
- JSON array for code
- HTML <option> tags for dropdowns
Executable extensions list best practices
Keep your extension list platform-aware and documented when using it in security or validation contexts.
- Annotate which platform each extension belongs to when using the list in security policies or documentation.
- Use the JSON format to feed extension arrays directly into file validation logic, keeping your code and reference data in sync.
- Treat this list as a baseline — always review platform-specific documentation before finalizing an allowlist or blocklist in a production environment.
Frequently asked questions
Does this list include script files like .sh and .py?>
Why does the JSON format output only the extension and not the full label?>
Are shared libraries like .dll or .so included?>
Related Developer lists
Copy common application/* MIME types in text, JSON, or HTML format for API content negotiation, downloads, and file validation.
Copy common audio MIME types in text, JSON, or HTML format for uploads, playback support checks, and processing pipelines.
Copy a practical common MIME types list in text, JSON, or HTML format for uploads, APIs, validation, and content handling.
Copy common compressed and archive file extensions in text, JSON, or HTML format. Useful for file validators, dropdowns, and developer references.
Copy common document file extensions with format names in text, JSON, or HTML format. Ideal for developers, docs, and file type references.
Copy all HTTP 2xx success codes in text, JSON, or HTML format for API docs, tests, and monitoring workflows, ready to paste.
Copy all HTTP 3xx redirect codes in text, JSON, or HTML format for API docs, tests, and monitoring workflows, ready to paste.
Copy all HTTP 4xx client error codes in text, JSON, or HTML format for API docs, tests, and monitoring workflows.
Copy all HTTP 5xx server error codes in text, JSON, or HTML format for API docs, tests, and monitoring workflows.
Copy a clean http request methods list (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS, TRACE, CONNECT) in text, JSON, or HTML for API docs and tooling.
Copy the complete IANA-registered HTTP status codes list in text, JSON, or HTML format for APIs, docs, testing, and observability workflows.
Copy common image MIME types in text, JSON, or HTML format for upload validation, image processing, and media tooling.
Copy all 6 native JSON data types from RFC 8259 in text, JSON, or HTML format for quick reference, docs, and dropdown menus.
Copy common regex and string escape sequences in text, JSON, or HTML format. Includes \n, \t, \r, \\, \0, \uXXXX, and more.
Copy common video MIME types in text, JSON, or HTML format for upload policies, streaming workflows, and player support checks.