About

Korean writing tools and a data workbench

modu.tools is an independently maintained utility site. Its primary identity is a Korean writing toolkit—character and byte counting, Revised Romanization, messaging limits—backed by guides. Beside that sits adeveloper data workbench for JSON, CSV, YAML, URL encoding, Base64, and hashing. Pages stay focused: one job, a working interface, and limits you can read before you paste.

What the site is for

Writers use the toolkit to check cover-letter length, SMS-style bytes, and romanized place names against documented rules. Developers use the workbench and related tools to format JSON, convert CSV or YAML, encode URL components, and fingerprint short text samples—without creating an account. Guides exist so the numbers and spellings on the tools can be traced to primary sources rather than folklore.

The catalog is curated on purpose. Thin or overlapping utilities may be marked noindex or folded into stronger pages. We do not publish empty shells to inflate the tool count.

How pages are made and kept current

Guide frontmatter lists sources when a page states a rule or limit. Typical citations include the National Institute of Korean Language (spelling, spacing, Revised Romanization), Kakao Business and SOLAPI documentation for AlimTalk and SMS-style byte guidance, RFCs for URI, CSV, Base64, JSON and UTF-8, plus MDN and the WHATWG URL Standard for encoding behavior. When a vendor page and a gateway disagree, the guide says so.

Worked examples are checked against the same logic the site ships—or an equivalent browser/Node API—before publication. Each guide carriespublished and updated dates; substantive edits move updated. The changelog records what each round shipped so readers need not dig through git.

How tools are checked

Transformation logic is exercised with automated examples: empty input, Unicode, malformed values, and known edge cases. Releases pass Astro type/build checks, generated-route and sitemap guards, a personal-info scan of the built output, and an axe-based static accessibility check. Keyboard use, live status text, and narrow screens remain part of manual review.

Browser-local data handling

Tool inputs are processed by JavaScript that runs in your tab. Pasted text and chosen images are not uploaded to modu.tools. Some tools keep drafts or preferences in this browser only (for example localStorage for the character counter and the theme preference). A share link, when offered, stores content in the URL hash on your device—not as a server-side document.

Loading a page still downloads its assets, and pages may load third-party scripts such as advertising. The privacy policy describes those. Copying a result into email, chat, or another SaaS transfers it to that service. Each tool restates this boundary beside its controls when the risk is easy to miss.

Publishing bar

A page ships when the tool works, the explanation cites sources where it states rules, processing stays in the browser for user input, and there is a path to correct mistakes. If those are not true yet, the draft stays unpublished.

Corrections

Behavior notes change when the implementation changes. Reports of a reproducible error, unclear limit, inaccessible control, or misleading sentence are reviewed against the code and a minimal sample before public copy is updated. Send reports to contact@modu.tools with a URL and a short quote; we aim to review them and reflect confirmed fixes in the page and changelog.

Editorial and contact

Guides and tool documentation are maintained under modu.tools Editorial. Site questions, privacy questions, and domain inquiries use the same address: contact@modu.tools.