Vayce is a set of browser-based tools for images, text and data, and audio. A file you open is read by the page, processed with Canvas, Web Audio, and Web Workers, and written back out as a download. It is not sent anywhere.
The tasks are the small ones that sit between other work: resize a screenshot, convert a format, check a hash, trim a clip, reformat JSON. Most sites that handle these ask for an upload and an account first. The browser can do the work directly, so Vayce does it there.
Local processing is the constraint
This is the rule the site is built around rather than a feature added to it. A tool that needs a server key, a paid API, or an upload is not built here, whatever its search volume.
Some work is ruled out by that. A licensed codec, a lookup against a private dataset, or a model too large to download belongs on a server, and those tools are not on Vayce.
What stays in gets three things from the rule. No queue and no size cap set by someone’s free tier. No account between you and a five-second job. A page that has finished loading keeps working if the connection drops.
Who it’s for
Marketers and writers preparing images and copy, freelancers and small business owners handling their own assets, developers and technical learners checking a value or a format, and anyone who inherited a website and now has to keep it running.
The tools assume you know what you are doing and have something else to get back to. Controls are labeled with what they do, exact values stay visible, and nothing is hidden behind a wizard.
What the tools cover
Three categories, each with a directory page split into subcategories so a long list stays readable.
- Images: format conversion and compression, resizing, cropping and layout, color adjustments, optical and artistic filters, camera and analog looks, metadata inspection, and generators like placeholders and test cards.
- Text and data: text cleanup and analysis, number and date conversion, color math, structured data formatting and validation, encoders, hashes and IDs, and web utilities.
- Audio: format conversion, trimming and merging, level and tone correction, effects, analysis, and signal generators.
All tools lists everything in one place, and the search box on the homepage matches names and keywords across the whole set.
Settings live in the URL
Tool controls write to the query string as you change them, so the address bar holds the state of the tool. Copy that link and whoever opens it gets your exact setup, not a blank tool. Values left at their default are stripped out, so the link carries only what you actually changed.
That link is also how a setup survives a closed tab, a different machine, or a message to a colleague.
Workflows chain tools into one recipe
A single tool does one thing. Workflows stack many of them into an ordered chain you can save, reopen, and share.
Image workflow draws its steps from the image tools: brightness, temperature, levels, grain, vignette, glow, halftone, and the rest. Steps run top to bottom, each one reading the output of the step before it, so grain before blur and blur before grain give different results. Expand a step to change its settings, reorder it, or bypass it to compare with and without. The preview is capped at 1024px for speed; the download re-runs the whole chain against the original pixels, so a 4000px photo exports at 4000px.
Audio workflow does the same for a signal path: gain, fades, EQ, filters, reverb, echo, and distortion. The chain you hear during playback is the chain that renders, out to WAV, MP3, M4A, Ogg, or FLAC. Reverb and echo tails keep sounding past the end of the source, so the render runs on until they fall below -60 dB instead of cutting them off.
Both ship with built-in presets, and both let you save your own. A saved chain behaves like a preset or a LUT with one difference: you can open it and change any step, so raising a vignette later is one slider rather than a re-export. Saved chains sit in your browser’s storage on that one device. The ?chain= link is how a look moves between devices or reaches someone else.
Tool pages that feed a workflow carry a badge under the title. Clicking it hands your current settings, and the file you loaded, into the editor as the first step.
Embeds put a tool on your page
A shared link and an embed answer different halves of the same problem. The link gives someone your setup; an embed gives them the tool itself, on your page, without sending them anywhere. Every tool embeds, and the processing still happens on the reader’s machine.
Three ways to place one:
- Paste the iframe. Open a tool, use Embed in its share bar to pick a surface, theme, and padding, then copy the generated code. The builder carries whatever settings you have dialled in, so the frame opens configured rather than blank.
- Load it with a script. One
<script src="https://vayce.app/embed.js">builds an iframe for every[data-vayce-embed]placeholder on the page. For a CMS that strips inline scripts out of post bodies. - Paste the link. Every tool publishes an oEmbed endpoint in JSON and XML, so WordPress, Ghost, and Discourse turn a pasted tool URL into a live embed with no snippet involved.
The frame reports its content height to the parent window whenever it changes, so an embed sizes itself instead of growing an inner scrollbar. Opening heights are measured per tool rather than guessed, because oEmbed consumers strip the resize script and keep whatever height arrives. Three underscore-prefixed parameters (_surface, _pad, _theme) control the frame’s own chrome without colliding with the tool’s settings.
Embeds are free for any site, commercial included. The credit link under the frame is yours to keep or delete, and nothing about the tool changes either way. /embed/ pages carry no analytics at all.
Guides and explanations
The blog covers the decisions behind the tools: which image format to use and why, what happens between a URL and a rendered page, what the browser can do without a server. Posts are grouped into topics, and longer subjects run as a series with a hub and parts, like web image formats explained.
Tools get linked from a post where they remove a step, not as a sales pitch.
Where it goes next
More tools, in the same three categories and under the same constraint. More workflow steps, so a chain covers more of a job. Better explanations of the formats and browser behavior underneath.
Requests from people using the tools decide a good part of what gets built next.
Privacy and terms
What that covers, and what it does not, is written out in the privacy policy and the terms of service.
Get in touch
Feedback on a tool, a bug, a question about an embed, or a suggestion for what to build next: contact@vayce.app.