Getting started

What aukimi is, what your browser needs, and how to get from a blank dashboard to a working project.

aukimi is a creative suite that runs in a browser tab. Fourteen studios: a game engine, sculpting, retopology, texture painting, rendering, procedural materials, raster and vector painting, pixel art, layout, PDF assembly, animation, video and audio: share one project, one file library and one clipboard. Nothing is installed, and nothing has to be exported to move between them.

What your browser needs#

A recent Chromium-based browser (Chrome, Edge, Brave, Arc) or Firefox. Safari works for the 2D studios and is the weakest choice for the 3D ones.

WebGL 2required by every 3D studio: Sculpt, Retopo, Pigment, Render, Matter, Engine
WebGPUused by Engine when available, and by some GPU filters; the app falls back to WebGL 2 when it is missing
IndexedDBwhere your work is stored locally. Private/incognito windows often clear it on close
Web AudioPulse and Fusion playback

A discrete or recent integrated GPU makes a visible difference in Sculpt, Pigment and Engine. None of the studios needs a plugin, an extension or a download.

Your first project#

The dashboard, with the module rail, the project list and the row of studios you can start straight into

  1. Open the dashboard. It lists your recent projects with a search box, filters (module, storage, type) and grid or list view.
  2. New project. A project holds the state of every module: the Engine scene, the Inkwell canvas, the Pulse arrangement, all of it, under one name. You do not pick a module up front.
  3. Pick a studio from the module rail down the left edge. The project opens in it; switching studios never closes the project.

There is a second, lighter option on the dashboard: start straight in a module. That creates a document rather than a project: a single-module file with no cross-module state. Documents can be converted to full projects later (Convert to Project); the reverse is not offered.

Where your work lives#

Everything is saved locally as you work, in IndexedDB with a localStorage fallback. Auto-save is on by default and its interval is configurable in Settings → General.

Cloud save is a separate, opt-in layer: with it on, the project is uploaded roughly every 60 seconds when something has changed, and the sync pill at the bottom of the window reports the state. Without it, the project exists only in the browser you made it in: the dashboard labels those On this machine.

Local storage is finite. When the browser reports the quota nearly full, aukimi warns you rather than failing a save silently. Clearing site data for aukimi.com deletes every local project that was never uploaded.

The tour#

More menu → Guided Tour, or Settings, replays a narrated walkthrough: the module rail first, then Inkwell in full, then one chapter per studio. It drives the real interface; it opens the modules and spotlights the actual panels, so it stays true as the app changes.

Where to go next#