Documentation
Rosehip
Five small tools for the file and text chores that come up every week — a SHA-256 checksum reader, a JSON formatter, a Base64 codec, a URL codec and a set of line utilities. All of them run inside the browser tab.
What Rosehip is
Rosehip is a static web application. The page is a single HTML document, one stylesheet and one JavaScript file; there is no back end, no database and no session. When you open a file or paste a string, the work happens on your own machine with the browser's built-in APIs.
That design has consequences worth stating plainly:
- Nothing is uploaded. The page has no upload endpoint, and the file reader never leaves the tab.
- Nothing is remembered. Reloading the tab discards every input, output and computed digest.
- Nothing is measured. There are no cookies, no analytics script and no third-party requests.
The five tools
- File checksum — compute the SHA-256 digest of a file and compare it with an expected value.
- JSON — format, minify and validate JSON, with the position of the first syntax error.
- Base64 — encode and decode UTF-8 text, with an optional URL-safe alphabet.
- URL — percent-encode and decode a single query component.
- Text — trim, deduplicate, sort, change case and count lines, words and characters.
What Rosehip is not
It is not a password manager, a file converter, or a way to prove that a file is trustworthy. A checksum confirms that two files are identical; it cannot tell you whether the file you received is the one that was intended for you. Judgement stays with you.
The tools are also deliberately narrow: SHA-256 only, no MD5 or SHA-1; JSON only, no YAML or TOML; text only, no images or archives.
Where to go next
If you have not used the site yet, start with Getting started. If you came here to compare a digest, the file checksum guide walks through the whole flow, including the cases where a mismatch is expected.