Prepare ionCube Files for Recovery on Linux, macOS, or Windows

Follow the browser-based ionCube preview workflow, preserve original files and paths, and avoid unsupported command-line API examples.

3 min readBy PHPDecompile TeamLast updated: Oct 22, 2026

The online ionCube workflow uses your browser and account. Your laptop's operating system does not, by itself, establish recovery support for a protected file. The important inputs are the original file, its application context, and the result you can inspect.

Prepare one original file

Keep an untouched copy of the complete project. Select a representative .php file from the component you are authorized to maintain. Do not paste only the visible wrapper into a new file, change its contents, or run an unknown program to “unlock” it.

Record its original relative path, application release, expected PHP version, and any error already shown by the application. Those details make a failed assessment easier to investigate.

Use the account workflow

  1. Sign in and open the trial screen when trials are available.
  2. Read the current allowance and confirm the upload authorization.
  3. Submit the original representative PHP file.
  4. Review the encoder label, status, any partial-result notice, and limited output.
  5. Decide whether a paid assessment of more files is justified.

The trial is a limited source preview. It is not a complete free project, and it does not prove that every file from a different build or vendor will work. Use the ionCube decoder page for the service overview and current limitations.

Notes for each operating system

Your workstation Preparation detail that matters
Linux Keep path and case information when copying inputs from a server; verify the correct original was selected
macOS Keep the original package rather than resaving protected data through an editor; separate local downloads from the production copy
Windows Preserve the file extension and use the original download rather than a text copy pasted from a browser

These are file-handling concerns, not different compatibility promises. You do not need the ionCube Loader on your workstation merely to submit a file to the browser workflow.

Expand to a paid project

Review the selected file count and quoted cost before ordering. A paid ZIP upload is a convenience for selecting PHP files: the browser extracts .php entries and uses their base filenames. It does not return your database, assets, or an assured original directory tree.

Keep a manifest mapping paths to the selected files. If several directories contain index.php or config.php, reconcile each result against the order and your manifest instead of overwriting the project by filename.

Avoid unsupported automation examples

The website's private dashboard endpoints use account sessions and order state. Do not treat an old example curl command or guessed upload URL as a published API contract. If you need automation, ask support to confirm an offered interface and its requirements before designing the integration.

FAQ

Does browser-based recovery change production files?

The submission processes the copy you provide. Deploying a replacement is a separate action for your maintainer.

Can I remove the original after a successful preview?

Keep it. A limited preview is neither a full recovery nor a completed application test.

Next steps

More in Prepare and scope a recovery.

Ready to decode ionCube and SourceGuardian files?

Try PHPDecompile free. No credit card required.