How YourTool Works
YourTool loads as a static website. The three editors use your browser to work with images and project data; there is no account or cloud copy of your work.
1. The page loads
Your browser downloads the static page and the code needed for that route. Editor and 3D preview code is kept with the relevant tool instead of being loaded by every page.
2. The tool runs on your device
When you select a file, supported processing uses browser APIs such as Canvas or a client-side library. The input is kept in browser memory and is not sent to a YourTool application server.
Large jobs still consume your device's CPU and memory, so performance depends on the browser and hardware.
3. Results are saved by you
Downloads and exports are created in the browser. You choose when to save the result. YourTool does not keep a server copy.
Local persistence
Minecraft Skin Studio stores its current session locally. Pixel Studio and Pixel Paint use IndexedDB for their current project. Drafts belong to this browser and origin, not an account; clearing site data removes them. Export Pixel Studio/Pixel Paint JSON for a portable backup, and save skin PNG copies. Theme and privacy preferences also use browser storage.
Third-party connections
The website may connect to separately configured advertising, analytics, or support providers. Those requests are distinct from local tool processing and may expose normal connection data to the provider. The configured Google publisher tag can load for site connection and Google Privacy & Messaging even while ad placements are disabled. Optional analytics uses the YourTool preference; advertising consent is governed by the separately configured Google/CMP setup. No selected image is passed to those services by an editor.