01 / Start with what you want to do
Think in verbs: calculate, plan, convert, generate, track, visualize or learn. Purpose-based routes help you narrow the library by the kind of work you are doing. Subject categories describe the topic; function types describe what a tool does.
The original project has 141 tools, but introductions appear here only after they are prepared. If a route has no published entries, the library shows an honest empty state rather than a list of unreviewed placeholders.
02 / Read for fit
Begin with the short description and intended users. Then look at the practical use cases: do they resemble the task in front of you? A tool can be well made and still be the wrong fit for a particular job.
Check limitations before investing time. Look for requirements such as a source image, a particular browser feature, physical measurements or a separate test process. An attractive preview does not establish the accuracy of a result.
03 / Open the original tool
A published introduction provides a direct original-tool link. The introduction explains the tool; the original site runs it. You can take that route as soon as you have enough information to decide.
External-tool links open in a new tab so the explanation remains available. The original site's interface and policies apply there. This library does not require an account to read its introductions.
04 / Try a small, non-sensitive example
Use a sample you can safely experiment with. Check units, settings and the difference between a preview and an export. If a tool saves work in the browser, make a separate export of anything you need to keep.
For physical processes, calculations and reference tasks, compare the result with an appropriate real-world check. A digital plan is most useful when you understand how it connects to the work outside the screen.
Choose your reading language
Use EN or 한국어 in the header to switch to the corresponding page. If no translation exists, a nonexistent translation link will not be shown. Both language homepages can also be opened directly.
The original tool's supported languages are listed separately from the language of the introduction. A Korean article does not by itself mean that the original interface is available in Korean.
Help keep the map accurate
If something differs from the introduction, note the tool name, the page address, the browser and the steps that led to the problem. A specific, reproducible report is more useful than a general statement that a tool is broken.
Contact is also the place to point out an unclear translation or a missing limitation. Do not include private files, passwords or sensitive project data in your message.