01 · Image inspectorLocal
Read image dimensions before you edit.
Check pixel dimensions, aspect ratio, megapixels, file size and an approximate uncompressed RGBA working size.
StatusChoose an image to inspect.
Browser tools + live utilities + workflow bench
Do something useful
before you pick a tool.
WEBBE-B is a working browser utility hub, not only a directory. Inspect an image, calculate a SHA-256 checksum, check print dimensions or clean a filename list directly on this page—then move into the full tools and curated workflows when the job needs more depth.
No account required: workflow progress is stored only in this browser. The underlying tools remain independently usable, and every plan explains what to verify before you make a destructive or high-stakes decision.
Quick Bench · runs on this page
Four useful checks without leaving the hub.
These small utilities are intentionally narrow. They run in your browser and return immediate, inspectable results. Use them for quick checks; use the dedicated WEBBE-B tools when you need batch controls, richer workflows or specialist options.
No account. No server-side file upload for these four operations. Files selected here are read by browser APIs on this device.
02 · File checksumSHA-256
Fingerprint a file exactly.
Calculate a SHA-256 digest with the browser Web Crypto API. Matching hashes are strong evidence that two file byte sequences are identical.
StatusChoose a file to hash.
03 · Ratio & print sizeCalculator
Turn pixels into ratio and physical size.
Enter pixel dimensions and an optional DPI target to get a simplified aspect ratio plus approximate print dimensions.
04 · Filename cleanerPreview only
Preview safer, consistent filenames.
Paste one filename per line. The preview removes common path-invalid characters, normalises spacing and resolves duplicate output names without touching files on disk.
Paste one filename per line.
Visible method
Each mini utility states what it calculates and where its limits begin. Results are not presented as opaque scores.
Useful fallback
The explanatory content remains readable without JavaScript. JavaScript adds the calculation rather than hiding the page's meaning.
Escalate when needed
Quick Bench handles one-off checks. The dedicated tools remain available for larger inputs, specialised controls and deeper verification.
Workflow Bench
Turn a goal into an ordered plan.
Choosing the right utility is often only half the job. Order matters: deleting before inventorying, resizing before cropping, or cutting material before checking kerf creates avoidable mistakes. These workflows are manually curated around the tools currently published in the WEBBE-B network.
Pick a goal. Tick steps off as you work. Your progress stays in local browser storage and can be reset at any time.
What are you trying to do?
Each choice builds a short sequence with verification notes.
Nothing is sent to WEBBE-B when you choose a workflow.
ReadyChoose a goal on the left.
The bench will build a curated sequence from the existing tools, explain why each step comes next, and keep a local checklist while you work.
Curated workflow0 / 3 complete
Reclaim disk space without deleting blindly
- Step 01Open tool →
FolderHeat
Identify the folders and files that actually consume the most space.
- Step 02Open tool →
ExactDupe
Hash candidate duplicates so matching names or similar photos are not mistaken for identical files.
- Step 03Open tool →
RenameDeck
Preview a consistent rename plan for the files you keep.
Verify before finishing
Delete only after you have a backup or another recovery path and have checked the duplicate groups yourself.
Stop or reconsider when
Do not use size or filename similarity alone as proof that two files are interchangeable.
Order is part of the answer
The bench does not simply list related apps. It places inspection before destructive actions and composition decisions before final output sizing.
Verification is explicit
Every workflow ends with a check that the browser cannot perform for you, such as confirming printer scaling, physical measurements or source rights.
Progress stays local
Checklist state uses localStorage on this device. There is no WEBBE-B account, cloud workflow history or server-side profile behind the feature.
Tool explorer
Search, filter or browse A–Z.
Search the complete registry, keep the alphabet index, or open the dedicated tool directory. Public tools only—no unfinished cards.
Number badges mark letters that currently contain public tools.
image
Actual Size Lab
Print images at exact physical dimensions.
Open tool →fileCiteSweep
Extract clean case citations from searchable PDF briefs locally.
Open tool →fileExactDupe
Find exact duplicate files locally with full SHA-256 hashing.
Open tool →financeFinSmart Studio
Run clear finance calculators and scenarios.
Open tool →fileFolderHeat
See which folders and files are using the most space.
Open tool →fileFolderList
Export folder file names, paths, sizes, and dates without uploading files.
Open tool →workshopFrameCut Visual Planner
Calculate and visualize picture-frame cut dimensions.
Open tool →imageImage Foundry
Clean, repair and reprocess images locally in your browser.
Open tool →Original guides
Use the tool, understand the workflow.
The directory tells you what a tool does. The guides explain the decisions around it: what to verify first, which output to keep, and where a browser utility stops being the right tool.
Image workflow
Move from source selection to metadata, cleanup, crop, resize and print preparation without treating every image task as one giant edit.
File cleanup
Inventory and analyse first, verify exact duplicates, preview rename rules, and only then make destructive changes.
Browser-local privacy
Understand what a local transformation means, what still crosses the network, and how to evaluate privacy claims.
Field Notes
Methods, failure modes and worked examples.
Tool interfaces are compact. The Field Notes document the reasoning behind them: why duplicate detection uses a full hash, how rename collisions happen, where image repair loses context, and what a browser can and cannot verify.
Files
Why exact duplicate detection ends with a full hash
Candidate grouping, full-file SHA-256 and why deletion stays manual.
Images
Where local image repair works—and where it breaks
Mask size, edges, textures and the limits of surrounding context.
Workshop
Why a nesting layout is a candidate, not a proof
Piece order, grain, defects and grid precision in heuristic search.
Publishing standard
Every tool must earn its place.
A working interface alone is not enough. Each public tool is expected to provide original explanation, clear navigation, technical disclosure and a usable mobile experience.
Complete a real task
The primary function must work without dead controls, fake results or mandatory registration. Important errors should produce understandable messages rather than a broken screen.
Explain the method
Inputs, formulas, processing steps and limitations should be visible in plain language, with separate methodology pages where the subject needs more depth.
Respect user data
Tools should state what stays in the browser, what a hosting provider may log, and which third parties—such as an advertising provider—may process data.
Remain navigable
Users should be able to reach the main function, original guides, About, Contact, Privacy and Terms without guessing or encountering unfinished pages.
What makes this useful
More than a link directory.
The hub documents the collection's purpose and standards; each subdomain contains the actual tool, user guidance and specialist explanations.
Focused scope
Each product is designed around one problem area. A print-layout tool does not become a finance menu, and a finance calculator does not carry an unrelated image editor.
Shared visual system
Navigation, typography, borders, content structure and policy access remain consistent, while each tool keeps a distinct accent colour and task-specific interface.
Central discovery
Product sites link back to WEBBE-B instead of maintaining a growing web of direct cross-links. The central index stays understandable as the collection expands.
Frequently asked questions
About the network.
These answers describe how WEBBE-B is organised and what users should expect from the tools.
What does the Workflow Bench do?
The Workflow Bench turns thirteen common goals into manually curated sequences of existing WEBBE-B tools. It explains why each step comes next, adds a verification note, and saves checklist progress only in local browser storage. It is a planning aid rather than an automated agent: it does not upload files, open accounts or perform destructive actions for you.
Are the workflows automatically generated?
No. The published workflows are curated and tested as part of the hub. They are updated when the underlying tools or recommended order changes, and each one includes a point where the user should stop or independently verify something the browser cannot know.
Which letters currently contain published tools?
WEBBE-B currently lists 17 published tools across A, C, E, F, I, M, O, P, R, S and T. A letter becomes active only when at least one public tool with that initial is in the registry; empty letters do not lead to placeholder pages.
Can several products use the same letter?
Yes. The alphabet is a browsing index, not a limit of twenty-six products. If multiple finished tools begin with A, the A section can list all of them.
Do the tools share accounts or uploaded files?
No shared account system is currently operated. Many WEBBE-B file, image and calculation tools perform their main work in browser JavaScript or browser file APIs. Because the exact processing model differs by product, each tool is expected to explain what stays local, what may contact third parties and what limitations apply.
Are results guaranteed?
No. Tools are designed for practical planning and education. Printer hardware, financial products, laws and personal circumstances can differ, so important decisions require independent verification.
How are problems reported?
Use the Contact page or email its.me.jsKim@gmail.com. Include the page address, device, browser, steps taken and the result you expected, but do not send passwords, payment details or identity documents.
Does WEBBE-B sell user data?
WEBBE-B does not operate a user-data marketplace. Hosting, security and advertising providers may process technical or advertising data as described in the Privacy Policy.
Browser-local processing
“Runs in your browser” has a specific meaning.
When a tool says selected files are processed locally, the task code works with those files inside the browser rather than sending the file contents to a WEBBE-B application server for the calculation or transformation.
Your selected files
File and image tools that advertise local processing use browser APIs such as File, Canvas, hashing or client-side JavaScript for their main operation. The individual tool page states its own processing model because not every product handles the same kind of input.
The website request
Local file processing does not mean the visit itself is invisible to the network. A browser still requests HTML, CSS, JavaScript and other site assets from the hosting infrastructure, which can create ordinary technical logs such as IP address, request time and user-agent information.
Advertising and third parties
Pages that carry advertising may load code from an advertising provider. That provider can process technical, consent or advertising data under its own terms. WEBBE-B keeps this separate from the result logic: an advertisement does not decide a calculator answer, file hash or image transformation.
Transparency
Independent and still evolving.
WEBBE-B is created and maintained by Jisung Kim. AI tools may assist with implementation drafts, testing ideas and wording, but public functionality and explanations are reviewed before release.
Advertising may be used to support domain and hosting-related costs. Ads do not determine calculator results or editorial explanations, and no page is designed primarily as an advertisement container.