Built to run in your browser
gilika is built so that the one thing you care about, your code, stays on your machine. Here is how it works, and how you can verify it yourself.
How to turn code into an image
Paste your code
Drop a snippet into the editor. The language is detected automatically, so highlighting just works.
Style it
Pick a theme, background, window style, and aspect ratio until the image looks the way you want.
Export
Download a PNG or copy the image straight to your clipboard. The image is built right in the page.
Client-side by design
Every step that touches your code happens in the browser. Syntax highlighting runs locally with Shiki using a JavaScript regex engine and no highlighting server, no round-trip. Your snippet lives only in the editor’s in-memory state, and export rasterizes the rendered preview to a PNG directly in the page. We designed it so the code text isn’t sent over the network, and you can confirm that yourself (below).
Accounts save styles, not code
Saving a style stores only the visual configuration; theme, background, font, aspect ratio, window chrome, and highlight settings. The code itself is stripped before anything is saved and never reaches our database. An account lets you reuse a look across snippets; it never holds your snippets.
Verify it yourself
Open your browser’s Network tab, paste a snippet, and export it. The only calls that reach a server are a check of your subscription status, (if signed in) an auth refresh, and an anonymous, cookieless page analytics beacon (Vercel Web Analytics) that records a pageview — none of them carries your code. When you export, you may notice a local data:URL entry: that’s the image being built in your browser. A data:URL has no domain and transfers zero bytes — it’s decoded on your machine rather than uploaded. That’s why you don’t have to take our word for it. Fonts are self-hosted, so there are no third-party CDN requests, and our analytics is cookieless and never sees the code you paste.