Builds, downloads and history
Every protected file is a job. Watch it run, download it, redo it with the same settings or save the settings for next time.
The pages
| Page | Use it to |
|---|---|
| Overview | See the queue and throughput at a glance, your recent builds and a few recommendations. |
| Protect | Start a build: Protect a file. |
| Jobs | Every build still inside its 24-hour window. Running rows stay on top and refresh every two seconds. Search by filename or template, download, delete one or all. |
| History | A durable record of every build you queued, including ones whose file has expired. Filter by status (Complete, Failed, Building, Waiting), preset, template and time; sort by most recent, highest size ratio or largest output; export a CSV; bulk delete. |
| Templates | Named, reusable sets of options. Create, edit, duplicate, delete, and import or export as JSON to move them between accounts. |
| Analytics | Your own numbers: daily throughput, which categories and options you use, preset habits, file types and the size ratio of output to input. |
| Plan | Your plan, your live headroom (running builds and builds today), the protection budget and the Premium trial. |
One build
Click a job for its details: the file, the options used, the time it took and the size before and after. From there:
- Download the protected file, while it is still within the retention window.
- Rebuild loads the same options into Protect; drop the file again and submit.
- Save as template keeps the options under a name.
- Delete removes the job and its output at once.
A build failed
A failed job shows its reason in the details. Common causes are a file the engine cannot process (not a normal Windows program, or damaged), an option combination that does not suit the file, and a program that already carries another protector. Rebuild with fewer options, or one preset lower, to find which one it dislikes.
Was this page useful?