Can I Recover Source From a Plugin I Purchased?

Buying an encoded plugin feels a lot like ownership. You paid for it, it sits on your server, and your site depends on it every day. So it is natural to assume that recovering its source is simply a matter of retrieving something that is already yours. But purchasing a plugin and having the right to recover its source are not automatically the same thing, and getting this distinction right is essential before you upload anything. This article explains the difference between purchase and license, when you likely do have recovery rights, when you should stop, and how to handle the situation responsibly.

Purchase vs License: The Core Distinction

Most commercial plugins are sold under a license to use the software — not as a transfer of ownership of the underlying source code. That distinction matters enormously here. When you buy a typical plugin, you generally acquire the right to run it, often on a certain number of sites, with updates for some period. What you usually do not acquire is ownership of the source or the right to recover it.

So the honest answer to "can I recover the source from a plugin I purchased?" is: it depends entirely on what your purchase actually granted. This is true regardless of whether the plugin was protected via the ionCube decoder or the SourceGuardian decoder format. The protection method does not change the licensing question underneath it.

When You Likely Do Have the Right

There are legitimate scenarios where recovering a purchased plugin's source is appropriate and within your rights:

• You bought full rights, including source. Some purchases explicitly transfer ownership of the code, not just a license to use it. If your agreement did that, the source is yours.
• You commissioned the plugin. If you paid a developer to build it under terms that gave you ownership of the resulting code, and you simply lost the original source files, recovering your own commissioned work is appropriate.
• You have written permission. The plugin's author or copyright holder gave you explicit, written permission to recover it. A short written grant resolves the question cleanly.

In each of these cases, you can honestly complete the ownership attestation at upload and proceed with a clear conscience.

When You Should Not Proceed

Equally important — arguably more important — is recognizing when to stop:

• You hold a standard usage license. If your license lets you use the plugin but says nothing about granting source rights, recovering the source is not authorized by that license.
• The terms prohibit reverse engineering or source recovery. Many plugin licenses explicitly forbid this. If yours does, that prohibition governs, and proceeding would violate the agreement you accepted.
• You cannot honestly attest ownership or permission. If you are not sure you have the right, that uncertainty is itself the answer for now.

In these situations, recovering the source is not authorized, and the service is not intended for it. Using recovery to bypass a license you agreed to is prohibited, and no framing changes that.

Why the Terms Matter More Than the Purchase

It is worth dwelling on why a paid purchase does not settle the question. Software licensing deliberately separates the right to use from ownership of the code, precisely because authors want to sell usage widely while keeping their source protected. That is a legitimate business model, and buying into it means accepting its terms. Your payment bought you what the license offered — typically use — and reading that license is how you learn what you actually hold. The receipt in your inbox is not the same as a grant of source rights.

The Attestation Is on You

Every upload requires attesting ownership or written permission, and this is the checkpoint where the plugin question gets answered honestly. The tool does not — and cannot — decide whether your particular purchase granted source rights. Only you can, because only you have access to your agreement and your circumstances. By attesting, you take responsibility for that determination.

If you are unsure, the safest and most responsible move is to ask the author for written permission before doing anything. Authors are sometimes willing to grant it, especially for legitimate maintenance needs, and a written grant removes all ambiguity. If they decline or the terms clearly forbid recovery, that is a clear answer to respect.

Handling Common Real-World Situations

A few scenarios come up often:

• The plugin author has vanished. Being unable to reach them does not create rights you do not have. Their absence removes a path to permission; it does not grant it.
• You need to fix a bug that affects you. A genuine and pressing need does not override the licensing terms you agreed to. If the terms forbid recovery, the need does not change that.
• You are maintaining a client's site. Your engagement to maintain a site does not automatically include the right to recover a third-party plugin's source. Check both your engagement terms and the plugin's license.

In all of these, the disciplined approach is the same: resolve the rights question first, ideally in writing, and only proceed if you genuinely have authorization.

FAQ

I paid for the plugin — isn't it mine? You own your copy and your right to use it, but not necessarily the source code. What your purchase granted depends on the license, so check it.

What if the plugin author is unreachable? Being unable to reach them does not create rights you do not have. Genuine ownership or written permission is still required.

Can I recover it just to fix a bug I'm affected by? Only if you are authorized. A legitimate need does not override the licensing terms you agreed to when you purchased.

How do I know if my purchase included source rights? Read your license or purchase agreement. It should indicate whether you received a usage license or an actual transfer of ownership including source.

Does asking the author for permission actually help? Yes. Written permission from the copyright holder resolves the question cleanly and is worth requesting when your rights are unclear.

What if the license explicitly forbids reverse engineering? Then recovering the source is not authorized under that license, and you should not proceed. The prohibition governs.

Proceed Only When You're Authorized

If your purchase or a written grant genuinely gives you the right to recover the plugin's source, the PHP decompiler can return readable, functionally equivalent code — though, as always, it may not be byte-identical, since comments and formatting can differ. The essential step is to confirm your rights first. Review the FAQ for more detail, and when you are certain you are authorized, start a free trial or create an account.