Offline desktop palette collector — pulls hex, rgb and hsl out of any text.
Paste anything with colours in it — CSS, a table out of a design doc, a list of hex codes from a chat — and get palettes without retyping a single value. A project is a plain JSON file you can keep in git, share and back up like any other source.
Paste anything that has colours in it — a chunk of CSS, a table out of a design doc, a list of hex codes from a chat — and get ready palettes without retyping a single value.
Nothing leaves the machine: no network calls, no telemetry. A project is a plain
*.palette.json file wherever you put it, so it lives in git, gets shared and backed up like any
other source file. Changes hit the disk on their own — there is no Save button.
rgb() / rgba(), ASCII and Markdown tables, CSS/SCSS
variables, grouped into palettes by section comments or by a shared name prefix. What exactly
is recognised: import formats..txt, .md, .css or .scss file into
the window to import it.No published releases yet, so the app is built from source. You need Node with pnpm and a Rust toolchain — the standard Tauri 2 prerequisites.
git clone https://github.com/n0sfer666/pallete.git
cd pallete
pnpm install
pnpm tauri build
pnpm tauri dev runs the app without producing an artifact.
The build is unsigned, so the system asks before running it the first time:
.AppImage directly, chmod +x it if needed.Projects stay where you created them. The workspace — remembered projects, the theme, the copy
format — lives in the app directory under the dev.n0sfer.pallete identifier, so reinstalling
does not wipe it.