The Polyglot Engine
Transform your travel memories into an interactive cinematic capsule in simple steps.
No Login
No account or sign-up required
Zero Data Stored
Your photos and route never leave your browser
Select Your Photos
Upload as many files as you want in a single batch. Everything is processed locally in your browser — no file is ever sent to a server.
Define Your Route
Add the cities and regions you want to fly through. You can attach a personal note or memory to each stop.
Seal the Capsule
A single .html file containing all your data is generated and downloaded. Share it, archive it, or open it whenever you like — no server needed.
Unlock the Experience
Open the downloaded .html file in any browser and drop the exact same file into the prompt to decrypt and launch your cinematic map.
The Polyglot Architecture
One file. Two completely different behaviors.
When opened in a browser, the embedded React engine boots up, decrypts the hidden binary data on the fly, and renders a cinematic, interactive map documentary.
Because the file headers comply with standard ZIP protocols, you can rename it to .zip or open it with WinRAR to extract your high-res photos and raw JSON data forever.
Deep Technical Analysis (For Engineers)
The Polyglot Engine operates by exploiting how different parsers interpret file signatures. Here is the *step-by-step memory manipulation* occurring under the hood:
- 01Parser Bypass (The Killer Tag)We inject an HTML_COMMENT_TAG opening tag right at the end of the HTML structure. When a browser reads the file, the DOM parser stops rendering immediately, completely ignoring the trailing binary data (ZIP structure) appended at the bottom. This prevents rendering crashes.
- 02The Magic PointerTo separate the executable code from the raw data, we embed a specific byte sequence:
___MLX_ZIP_START___. When the file is dropped into the app, we read it as a rawArrayBuffer, scan backwards to find this exact memory pointer, and slice the buffer. - 03In-Memory VirtualizationOnce the binary slice is isolated, it is synchronously decompressed using
fflate. The extracted image bytes are dynamically converted intoBlob URLsin the browser's memory. These temporary pointers are directly injected into the React Virtual DOM, rendering the map gallery *without a single byte touching a physical server*.