Small tools, built with a clear purpose
inblooms is an independent collection of practical browser tools. It began with a simple preference: when a small repeated task can be made faster, clearer or more private, build the tool and make it available.
What belongs in inblooms
A new project starts with a real task, not a need to fill a page. The tool should solve a focused problem, work without an account, and offer a useful result immediately. That is why the collection includes document, image, text, calculation, design and developer utilities rather than unrelated articles written only for search traffic.
How the tools are built
Most inblooms projects are static applications made with HTML, CSS and JavaScript. File and text processing is designed to happen on the user's device whenever the browser can perform the task safely. Larger third-party libraries are reviewed and stored with the project where practical, reducing unexpected network dependencies.
How releases are checked
Before release, core calculations and transformations are checked with known examples, the main workflow is tested in a real browser, and desktop and mobile layouts are reviewed. Language switching, metadata, favicons, structured data, privacy explanations and broken links are also checked. Complex file formats and browser differences can still produce edge cases, so reports from users remain important.
Privacy as an implementation choice
Privacy claims refer specifically to the content entered into the tools: images, documents, text and generated values are processed locally unless a tool clearly says otherwise. The public website may still use aggregate traffic measurement and advertising services, which are described separately in the Privacy Policy.
Who maintains the site
inblooms is maintained by an independent maker in South Korea. Product decisions, implementation, testing, translations and ongoing fixes are handled as one connected project. Questions, correction requests and reproducible bug reports can be sent through the contact page.
Decisions you can see in the tools
The implementation follows the task rather than a single template. InvoiceBloom renders its visible document before creating a PDF so Korean and other scripts remain intact. TimeBloom calculates from timestamps so background tabs do not simply lose elapsed time. PassBloom uses the browser's cryptographic random generator instead of Math.random, while image and document tools keep file processing local where the browser supports it.
Limits are part of the documentation
A browser tool should not pretend to support a workflow it cannot perform reliably. Unsupported server-dependent formats, browser limitations and external-library requirements are stated in the relevant guide or FAQ. Material changes and the checks performed after them are summarized in the public updates page.