DOTKIND / FIELD NOTES

How it works

The workflow, examples and limits behind every tool.

01

Pixel editor ↗

Each pixel stores a palette index; zero is transparent. Undo retains recent edits in the active page.

Example: Draw a 16 × 16 icon, switch colours and erase its background.

Grid sizes 8–64 pixels per side. Resizing crops or pads every frame after confirmation.

02

Animation frames ↗

Frames are separate pixel arrays. Duplicating copies the current frame; blank frames start transparent.

Example: Duplicate a face, change the eyes and alternate the two frames to make it blink.

Up to 24 frames; at least one frame is retained. No imported copyrighted sprite library.

03

Animation preview ↗

Loop length = frame count / fps. Onion skin shows the preceding frame behind transparent pixels.

Example: Twelve frames at 6 fps form a two-second loop.

Preview timing depends on browser scheduling; it is not a video or GIF export.

04

PNG & backup ↗

PNG export uses nearest-neighbour scaling and transparent pixels. Metadata gives each frame’s rectangle and duration.

Example: A four-frame 16 × 16 project produces a 64 × 16 sheet at scale 1.

Export scale 1–8. Backups preserve all frames and palette; undo history is not included.

05

Local work, explicit limits

Each workspace reports its input and file limits. Imports validate the supported format before asking to replace saved work. Plain text is displayed as text, never executed as markup. Both languages use the same tools; the root address always opens in English, with Chinese under /zh/.

Back to the toolkit →