Question 1

Is anything uploaded to a server?

Accepted Answer

No. The page is static and the whole dumper runs in a Web Worker inside your browser. You can open devtools, switch to the network tab and watch that nothing is sent, or load the page and go offline before dumping.

Question 2

Which binaries are supported?

Accepted Answer

ELF32 and ELF64 (Android and Linux) with metadata versions 16 through 31. PE, Mach-O, NSO and WebAssembly containers are not implemented yet and report a clear error.

Question 3

Why are some names <obfuscated:…>?

Accepted Answer

Some games encrypt part of the metadata string table and decrypt it lazily at runtime, so a file recovered from memory contains a mix of plain text and ciphertext. Those slots also lose their NUL terminator, so they are detected and replaced with a stable placeholder instead of corrupting the surrounding names.

Question 4

My global-metadata.dat is rejected by other tools. Will it work here?

Accepted Answer

Probably. A common protection permutes the header offset/size pairs and replaces the sanity magic. The layout is rebuilt by re-chaining the header integers and identifying each section from its contents — metadata token table ids, the string-literal chain and index arrays sized by the table that references them.

Question 5

How big a file can I dump?

Accepted Answer

A 200 MB binary needs roughly 2 GB of memory, which a 64-bit desktop browser handles. Turning off script.json and il2cpp.h reduces both memory use and runtime considerably.

Question 6

How do I dump a game that is already running?

Accepted Answer

Dump the library region from process memory and keep the --libil2cpp.so file name; the image base is read from it. Dumping metadata from memory also recovers names that are only decrypted at runtime.