Images
A browser-local image workflow
Select the source, inspect metadata, repair only what needs repair, decide crop and ratio, then prepare the final export or print size.
Original guidance
Guides for the work around the tool.
A small utility can perform a calculation or transformation, but users still need to know when to use it, what to verify, and where its limits begin. These guides document those decisions in plain language.
Files
A safer file cleanup workflow
Inventory first, locate large files, verify exact duplicates, preview rename rules and only then make destructive changes.
Planning
Assumptions, scenarios and constraints
Use calculators and planners to compare transparent scenarios instead of treating one output as a guaranteed forecast.
Privacy
What browser-local processing really means
Separate the local transformation from the ordinary network requests, browser storage and third-party services around the page.
Selection
Which WEBBE-B tool should I use?
Match image, file, planning, document and creative tasks to the smallest focused tool that actually fits the job.
Why publish guides
Useful software includes the limits.
WEBBE-B does not treat a working button as sufficient documentation. The same input can be appropriate in one context and wrong in another, so the surrounding explanation matters.
Decision context
Guides explain which problem a tool is designed to solve and when a different workflow is a better fit.
Verification steps
Important outputs should be checked. The guides identify practical checks such as preserving originals, reviewing rename previews and recording assumptions.
Technical boundaries
Local processing, hashing, image repair and calculation each have limits. Those limits are part of the product rather than fine print hidden after the result.
Go deeper
Read the Field Notes.
The five guides explain end-to-end workflows. Field Notes document narrower engineering questions such as full-file hashing, rename collisions, screenshot seams, packing heuristics and image-repair boundaries.
15 first-party technical notes
Each note is tied to a published WEBBE-B tool and includes concrete failure modes or worked examples rather than a generic software roundup.