JadePack Build Tool
JadePack is the official graphical desktop client released by JadeView, used for building, obfuscating, and signature-protecting JAPK asset packages.
Download and Installation
- Download URL: https://store.jade.run/downloads/jadepack/latest
- Installer type: NSIS installer (
.exe) - Platform: Windows 10 / 11
Run the installer and follow the wizard to complete the installation.
JadePack is a monthly subscription product. After downloading and installing, follow the on-screen instructions to complete your subscription and unlock all features.
Supported Features
Obfuscated Package (No Signature Required)
Even without a signature, JadePack applies a 3-layer reversible transform (XOR + byte permutation + bit rotation) to the packaged content, producing a non-plaintext obfuscated package. This is suitable for basic protection scenarios and requires no public key when loading.
| Feature | Description |
|---|---|
| Content protection | 3 layers of reversible transformation, stored as non-plaintext |
| Loading method | JadeView_load_from_bytes, no public key required |
| Use case | Internal tools, prototype distribution |
Signed Package
Provides a complete security solution with Ed25519 signature + AES-256-GCM encryption, verifying the source and integrity to prevent tampering.
| Feature | Description |
|---|---|
| Signature algorithm | Ed25519 |
| Encryption algorithm | AES-256-GCM |
| Content protection | Dual protection of signature + encryption |
| Loading method | JadeView_load_from_bytes + public key |
| Use case | Production environments, commercial distribution |
Unpacked Files
Supports storing certain files (such as .node native modules) as "unpacked", so they are not obfuscated/encrypted during packaging, allowing native modules to be loaded directly from the file system.
Compiling the Installer
Packages the application directory into an NSIS installer, containing the complete content including the main program, asset files, the WebView2 runtime, and more.
Configuration options:
| Option | Description |
|---|---|
| Application directory | The root directory path of the application to be packaged |
| Main program | The entry executable file (e.g. rtexA.exe) |
| Application unique identifier | Matches parameter 5 used when initializing JadeView (e.g. titles.jade.run) |
| Excluded files | Files/folders excluded during packaging (wildcards supported), such as AutoTheme.bak, JadeView.ec, etc. |
| Application name | The program name displayed after installation |
| Application version | The installer version number (e.g. 1.0.5) |
| Compression level | Compression strength; higher values yield a greater compression ratio but take longer. Options are zip / lzma / solid |
| Create desktop shortcut | Whether to create a shortcut on the user's desktop |
| Installation mode | The mode the user can select during installation (e.g. "Choose at install time") |
| Application icon | The icon file for the installer and shortcut (.ico format) |
| Output directory | The output path for the generated installer |
| Installation language | The language of the installation wizard interface, supporting Simplified Chinese, English, and more |
| WebView2 runtime | How to handle cases where WebView2 is not installed on the target system. "Online install — download during installation" means it is automatically downloaded and installed from Microsoft's servers |
| Minimum version | The minimum required operating system version (optional) |
Workflow:
- Switch to the Installer tab in the Build Center
- Fill in the configuration options above
- Click the Package and Generate Installer button
- Wait for packaging to complete, then retrieve the
.exeinstaller from the output directory
Relationship with the JadeView API
JAPK packages built by JadePack are loaded through the following APIs:
- Load from a local file:
set_protocol_service_path, see JAPK Asset Package Format - Load from memory:
JadeView_load_from_bytes, see Loading from Memory
Signed packages are verified against the JadeTweak platform root public key embedded in JadeView; no runtime public key setup is required.