A signature you make with one finger

Ink Stamp

Press and hold on the pad. Something hatches under your finger and settles when you lift. The gesture is the seed: a press and a flick can produce entirely different things — a branching plant or a thrown splat — and the muse box below the pad takes an idea, a letter or a symbol and grows the mark from it. One part of every specimen never belongs. Touch it again to copy it.

Runs in your browser: the product’s own build, no install, no account, and no network call

  • What it does: turns one gesture into a four-row specimen made of characters, then fits it to the destination before it is copied — 24 characters a line for Messenger, 40 with a non-breaking-space indent for Gmail, 32 for Discord. Three modes: Fine, a dot-matrix specimen at 48 by 16 dots on Messenger; Specimen, the glyph grid, two generators (a plant and an ink splat) with five vocabularies; and the Blot Test, a braille inkblot. The muse box seeds the growth from a typed idea, letter or symbol — everything is compiled on the device, nothing is sent.
  • What to try: press and hold for one specimen, then press again for a different one; a slow drag hatches something dense, a fast flick something sparse. Keep, reload, and open the kept specimen again; copy recipe gives the string that rebuilds it; share link opens it for someone else.
  • What it will not do: it makes no image, takes no account and charges nothing. The shelf holds twelve specimens, in this browser only. The frame belongs to the mode, not to a setting, so a specimen cannot be given a rectangle of its own; the status line says which mode and destination are in force.
  • Where it runs: entirely in this page. The growth is computed on the device, the clipboard is local, and nothing you draw or keep leaves the tab.
  • What it collects: nothing, unless you choose to send feedback — then the message, the page and a build id, plus the server-side details the terms name. The full terms and data note.

The record

Fifty-nine checks, twenty-five killed mutants, thirteen browser assertions

  • The gate tests contracts, not pixels. Fifty-nine interface checks cover gesture capture, growth, layout, render, fit, encode, three destination profiles, the pipeline, and the recipe layer. The handoff’s own test matrix is the specification, case by case.
  • A check that cannot fail is not a check. The falsifier plants twenty-five defects across the engine, the recipe module, the blot layout and the feedback payload — a plain space instead of a non-breaking one, a shape that never degrades, a recipe that accepts a foreign version — and requires every one of them to turn at least one check red.
  • A headless browser runs the shell, not the source. Thirteen assertions drive a real pointer press, then Keep, the shelf, a reload, a load, a recipe link and a damaged link. That is the only part that can catch a page that is wired wrong.

Under the hood

What it is built on

Stack
No framework, no dependencies, no build step in the shipped file: one 74 KB page that renders the same with the network off. The engine is pure functions and the interface is a thin shell over them.
Why text
An image is compressed, cropped or blocked by the place you want it. Characters survive copy, paste, search, screen readers and format churn, and they cannot be blocked by an image policy.
Data
Kept marks live in this browser’s own storage. A recipe is the gesture plus the settings, base64url, and decoding it replays the growth engine deterministically, so the same string always rebuilds the same stamp.
Tested by
59 interface checks, a falsifier that kills 25 of 25 planted defects, and 13 end-to-end browser assertions. All three run from the project, and the commands are in its README.

Questions about Ink Stamp

Whether the marks survive a particular client, or what the destination limits should be for an app not listed here — ask, and we will answer.

Open the feedback form