Documentation PHP Decoder

Contents

• Quick Start
• Install
• System Requirements
• Graphical Interface (GUI)
• CLI Reference
• Workflows & CI
• Readable Output
• Logs & Checksums
• Performance Tips
• Security & Privacy
• Legal & Acceptable Use
• Licensing & Updates
• Purchasing & Payment
• Troubleshooting
• FAQ
• Support

Quick Start

UnZend runs fully offline on your machine. Start with the GUI for a guided experience or use the CLI for scripting. Verify your setup, then decode a single file and a small folder.

unzend --version
unzend --help

unzend decode --engine ioncube \
  --input /path/to/locked.php \
  --out ./decoded/

unzend decode --engine sourceguardian \
  --input ./project-locked/ \
  --out ./project-decoded/

Install

Note: Depending on your plan, you may be prompted to activate on first run. Follow on‑screen instructions or the Welcome email you received after purchase.

System Requirements

• Windows or Linux (64-bit)
• Modern CPU; 8 GB RAM recommended
• Sufficient disk space for decoded output and logs
• Runs fully offline on your machine

Graphical Interface (GUI)

No coding experience is required. The GUI lets you launch jobs, select files or folders, choose the decoding engine, set an output location, and view results and logs — all offline on your machine.

Tip: For mixed projects (both ionCube and SourceGuardian), run separate jobs per engine.

CLI Reference

UnZend is CLI‑first. Run unzend --help for the complete list of commands and flags. Common patterns are shown below.

Decode a single file

unzend decode --engine ioncube \
  --input /path/locked.php \
  --out   ./decoded/

Decode a folder

unzend decode --engine sourceguardian \
  --input ./locked-src/ \
  --out   ./decoded-src/

Dry‑run & logging (recommended)

Before large jobs, perform a quick run and inspect logs. Use logging options from --help to capture summaries and checksums.

Workflows & CI

UnZend is designed for repeatable engineering workflows. The examples below demonstrate common patterns for automation.

Simple Bash script

#!/usr/bin/env bash
set -euo pipefail
INPUT=${1:-./locked}
OUTPUT=${2:-./decoded}

# Preview
unzend --version

# Decode
unzend decode --engine ioncube --input "$INPUT" --out "$OUTPUT"

# Basic sanity check
php -l $(find "$OUTPUT" -type f -name '*.php') | tee decode-php-lint.log

GitHub Actions (example)

name: Decode with UnZend
on: [workflow_dispatch]
jobs:
  decode:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Install PHP
        uses: shivammathur/setup-php@v2
        with:
          php-version: '8.2'
      - name: Run UnZend
        run: |
          unzend --version
          unzend decode --engine ioncube \
            --input ./locked \
            --out   ./decoded
      - name: Lint Decoded PHP
        run: |
          find ./decoded -name "*.php" -print0 | xargs -0 -n1 php -l

Readable Output

• Rebuilds symbol tables where feasible to restore developer‑friendly names.
• Removes common obfuscation layers for long‑term maintainability.
• Preserves project structure to minimize diff noise.
• Generates logs and checksums to aid auditing.

Logs & Checksums

• Job summary: Counts of processed, decoded, and skipped files.
• Warnings & reasons: Notes for files that could not be decoded (e.g., unsupported version).
• Checksums: Optional hashes to verify integrity of input and output sets.
• Storage: Logs are saved next to the output or to a custom path you specify.

Performance Tips

• Use a local SSD for both input and output directories.
• Exclude large non‑PHP directories from input paths.
• Run small samples first to validate settings before full runs.
• Keep your OS up‑to‑date; ensure sufficient free disk space for outputs and logs.

Security & Privacy

UnZend runs locally on your machine. Your code remains on your device, and jobs execute offline. Review logs on your own system and store outputs where your team policies require.

• Local only: No need to upload source files anywhere to decode.
• Project structure preserved: Keep changes reviewable and auditable.
• Team workflows: Save logs alongside outputs to meet internal audit requirements.

Legal & Acceptable Use

Licensing & Updates

• Includes a software license for UnZend v3.x (devices and update window depend on plan).
• Documentation and quick‑start guides are provided with your purchase.
• Email support from the engineers who build the decoder.

Purchasing & Payment

UnZend accepts crypto payments only. Step‑by‑step payment instructions are shown at checkout after selecting your plan.

Troubleshooting

FAQ

Support

Your purchase includes documentation, quick‑start guides, and email support from the engineers who work on the decoder. Use the contact method provided after checkout, or the contact form on our website.

Back to top ↑