Decompile Electron 36 .jsc Files
Electron 36 runs on the V8 13.6 line. JSC Decompiler reads the V8 build straight from the bytecode header and turns compiled .jsc files back into readable JavaScript — no matching runtime required.
Bytecode fingerprint
Every .jsc file opens with a 4-byte little-endian magic header that identifies the V8 code-cache format. Electron 36 files sit on the V8 13.6 line, paired with Node.js 22.
0xC0DE0692How to decompile a Electron 36 .jsc file
Upload at jscdecompiler.com
Drag and drop your Electron 36 .jsc file into the web app. Nothing to install.
Auto-detect the version
JSC Decompiler reads the magic header and selects the V8 13.6 deserializer automatically — you never pick a version by hand.
Download the JavaScript
View the reconstructed source in the browser, copy it, or download the .js file.
Electron 36 version notes
- Electron 36 runs Chromium 136 on the V8 13.6 line with magic 0xC0DE0692 — the same magic seen on Node 22.16+ and Node 24, so those files share a bytecode format family.
- It bundles Node.js 22 for the main process.
- Pointer compression is on, so the code-cache pointer width differs from a stock Node build on V8 13.6.
Electron 36 decompilation FAQ
What V8 version does Electron 36 use?
The V8 13.6 line (Chromium 136), magic 0xC0DE0692.
Why does my Electron 36 file share a magic with a Node 24 file?
Both run the V8 13.6 line, which writes the 0xC0DE0692 header. The decompiler still resolves the exact build from the full header.
Related versions
Decompile Electron 36 bytecode now
Upload a Electron 36 .jsc file and get readable JavaScript back in seconds. No signup required for the free tier.