PowerBuilder Decompiler Online
Inspect PBL and PBD objects and extract PowerScript source retained in the library.
Open a PowerBuilder library
Upload a standalone .pbl or .pbd library, or open one inside a supported archive. Libraries are recognized by their header. Browse powerbuilder.json for object names, types, library-header and compiled bytecode versions, and the paths of extracted files.
Retained source appears in source/ with text previews and downloads. Original entry bytes are kept in raw/, and the original library remains available in original/. Download individual files or the entire result ZIP.
Which source can be recovered?
PBL libraries can retain PowerScript exports such as .sru user objects and .srw windows. These are extracted and converted to UTF-8 when their encoding is known. Original bytes and conversion details remain available. An unknown legacy encoding leaves the raw payload available without a potentially lossy text conversion.
Can a compiled PBD be restored to a project?
Compiled-only PBD libraries provide an object inventory and binary object downloads. Compiled P-code source recovery is outside the current scope. The viewer does not reconstruct missing source, render DataWindows or rebuild a PowerBuilder project. Uploaded applications and recovered code are never run.
Compatibility and limits
Qualification covers Unicode libraries with a 0600 header and compiled object versions 333 and 335, plus authored ANSI and Unicode source cases. The header version is separate from the object bytecode version. Other libraries may yield partial results with specific notes.
Inspection is bounded to 64 MiB per library, 2,048 directory entries, 8 MiB per entry and 128 MiB of extracted output. Damaged or unsupported entries do not prevent other validated entries from being downloaded.