How to Evaluate a PHP Decoder Trial Preview
Use a limited ionCube or SourceGuardian preview to assess file support and visible code quality without mistaking it for complete application validation.
A trial preview answers a narrow question: does this particular protected file produce useful visible output through the current workflow? It cannot, by itself, prove that the entire project is recoverable or that the application will behave correctly after replacement.
Understand the allowance
The account's trial screen shows whether trials are enabled, how many are available, and the output allowance. These settings can change. This guide does not promise a permanent number of free uploads or preview lines.
The trial processes a submitted file and limits the returned source. Use a representative original PHP file, not a ZIP selected on the assumption that a whole project will be returned free of charge. The paid upload screen has a separate multi-file workflow.
Select a useful sample
Choose a file involved in the maintenance task, rather than only the smallest wrapper in the package. Record the original path, application release, and expected PHP version. For mixed projects, sample distinct vendor components or builds separately.
Keep the file untouched. Resaving protected data through an editor or removing a wrapper can make the assessment about a damaged copy rather than your original input.
Inspect the preview deliberately
| Check | What a preview can tell you | What still needs investigation |
|---|---|---|
| Encoder label | How the submitted file was classified | Support for other files or settings |
| Visible PHP structure | Whether the shown classes or functions look useful | Unshown functions and complete syntax |
| Partial warning | Whether additional uncertainty is reported | Whether a maintainer can complete or verify the result |
| Processing outcome | Whether this input completed or failed | Whole-project completion time and deployment readiness |
A deliberately truncated preview may not be a complete syntactically valid PHP file. Do not treat a syntax failure at its cutoff as proof that the full paid result will be identical, or treat a readable opening section as proof that every later section can be reconstructed.
Set a decision before buying
Define what would justify expanding: recognizable business logic, appropriate file classification, and acceptable limitations for the maintenance goal. If the result is unclear, ask support with the order reference and error or warning. Avoid repeating an unchanged submission without new evidence.
For a larger project, retain your path manifest and selected file groups. A preview is one input to a purchasing decision, not a guarantee of recovery or a substitute for code review.
FAQ
Does a free trial require an account?
The current workflow uses an account and the same ownership-or-permission attestation required for paid submissions.
Can I deploy the preview?
It is limited output for assessment. Treat deployment as a separate task requiring complete reviewed files and staging tests.
Will a paid result look byte-for-byte like the original source?
Not necessarily. Reconstruction can lose comments, formatting, and names, even when useful code is recovered.
Next steps
More in Prepare and scope a recovery.
Related Articles
Decoded PHP Quality: What Can Be Recovered and How to Check It
Distinguish readable reconstructed PHP from identical original source, complete control flow, and tested application behavior.
Bulk PHP Recovery: ZIP Uploads, Paths, and Duplicate Filenames
Prepare a multi-file recovery with a path manifest, representative previews, cost checks, and a precise understanding of what ZIP downloads contain.
Decoder Guides
Ready to decode ionCube and SourceGuardian files?
Try PHPDecompile free. No credit card required.