Solana Studio is the workbench for reading a program closely. It puts the disassembly, the decompiled source, the hex, the findings, and the call graph in one place, with navigation built for Solana — functions, accounts, CPIs, and PDAs — so you can walk a program without leaving the page.
Why it exists
Reading SBF bytecode by hand is slow, and Solana adds its own structure: which accounts an instruction touches, which programs it calls into over CPI, how its PDAs are derived. Studio surfaces all of that alongside the code, so you can follow a cross-program call or trace a PDA without switching tools.
Who uses it
- Auditor — inspects disassembly and findings and follows CPIs across programs.
- Researcher — maps the call graph and traces PDA derivations.
- Reverse engineer — reads the reconstructed source next to the original disassembly.
How to open it
- From an asset → Open in Studio.
- From a Solana analysis run after it completes.
- Direct URL —
/solana-studiowith a program loaded.
Working in the studio
The left sidebar navigates the program by Functions, Accounts, CPIs, PDAs, plus Annotations and Bookmarks, each with a keyboard shortcut. The centre holds the views — Disassembly, Source, Hex, Findings, and Call Graph — switched by the number keys; the Findings view has a severity filter from critical down to info. A Details panel on the right shows the specifics of the selected item, and a status bar keeps a live count of findings, functions, and the compute-unit estimate.
Limits
- Requires a signed-in account and a program that has been analyzed.
- The decompiled source is reconstructed from bytecode — a faithful approximation of what the program does, not the original source.
- The compute-unit estimate isn’t available for every program; a
-there just means no estimate, not a failure.
Related pages
- Analyze Solana Program — produces the data the studio renders.
- Solana Program Overview — the summary page for the same program.
- Solana Fuzzing — fuzz the same program.