Protect a file
Drop a program, pick how far to go, submit, download. The first build takes a few minutes.
Open it now:Obfuscator, Protect
Steps
- Drop the file. Only
.exeand.dllfiles are accepted, up to 50 MB. Atlas inspects it first and tells you what it found: the type, the architecture and what it can and cannot protect. - Choose a starting point. A preset, a saved template or Custom.
- Adjust. Open the sections on the left and change any option. The right-hand side shows your protection budget, conflicts between options and anything that must be fixed before you can submit.
- Submit. The job joins the queue. Progress is on Jobs.
- Download. When it shows Complete, download the protected file. It is kept for 24 hours.
Presets
| Preset | What it applies |
|---|---|
| Fast | Static changes only: symbols stripped, sections renamed, strings encrypted, imports hidden, PE header cleaned. About twice as fast to build. Good while you are still debugging your own program. |
| Balanced | Fast plus compression, filler code, anti-debug and self-integrity. Real friction at a sane build time. The usual choice. |
| Stealth | Focused on analysis hosts: anti-VM, anti-sandbox, stack spoofing, import hashing and the Balanced basics. It stays quiet on sandboxes. |
| Maximum | Everything on. The longest build and the biggest output. |
| Custom | You choose each option. See Options and levels. |
The protection budget
Each option costs points: its level times the weight of its category, with heavier categories such as virtualization and integrity costing more per step. Your plan sets how many points one build may spend. The meter on the right shows what you have used, and submitting is blocked when you are over, so reduce a slider or move to Premium. Plans, limits and retention has the numbers.
Conflicts and warnings
- Options that undo or break each other are flagged, with the reason.
- An option that needs another is listed under dependencies; submitting is refused until they are resolved.
- A pre-flight check reads your file and blocks a build that cannot work, for example a file type or setting the engine cannot handle.
- An option that may be flagged by security software carries a note, and Protect asks you to confirm before it submits an aggressive build.
Branding
The Packaging section sets what Windows shows for the file: product name, company, description, version, original filename, copyright, and (Premium) the icon. Set them to your own. Leaving them as they are in your original build is fine.
Was this page useful?