AI Background Remover
Segmentação RMBG no navegador.
Zavilo Browser SDK
The file tools your product needs, in one SDK.
Add image, PDF, QR, video, audio and developer utilities without assembling a different library and UI for every feature. Zavilo exposes a growing Tool Library through one consistent SDK contract.
86Tools
10Categories
H · I · EIntegration modes
One SDK contract
<script src="https://sdk.zavilo.app/v1/zavilo.js"></script>
const client = await Zavilo.init({
publicKey: "pk_live_xxxxx"
});
const result = await client.run("image-enhancer", { file });
await client.open({
tool: "document-scanner",
input: { file }
});
await client.mount({
tool: "pdf-editor",
target: "#zavilo-tool"
});NEW · Browser AI
Processamento de fotos com IA no mesmo SDK.
Remova fundos, proteja rostos e amplie imagens 2× diretamente no navegador.
AI Face Blur
Detecção automática com desfoque ou mosaico.
AI Image Upscaler
Super-resolução 2× em blocos.
Tool Library
A practical Tool Library for real products
From everyday conversion to interactive document and media workflows, Zavilo gives your application reusable capabilities that are ready to integrate.
AI Photo Tools3
Browser AI for background removal, face privacy and 2× image upscaling.
AI Document Tools2
Extract structured tables and redact sensitive data with browser-side document AI.
Image Convert9
Format conversion, resize, compression and output optimization.
Image Tools13
Enhancement, crop, background, OCR, scanner and production image workflows.
Icon Tools3
Favicon, app icon and web asset generation.
PDF Tools12
Merge, split, convert, watermark, signature, protection and editing workflows.
QR Tools2
Generate and read QR codes through the same SDK contract.
File Tools1
Bundle files from different folders and create password-protected ZIP archives in the browser.
Video & Audio15
Trim, resize, compress, extract, transcribe and other media workflows.
Developer Tools21
JSON, Base64, URL encoding, UUID, hash, timestamps and other utilities.
One integration instead of many separate libraries
Keep one initialization flow, one Tool discovery model and one result contract as your product adds more file capabilities.
One Tool Registry
Discover enabled Tools dynamically with client.listTools() and inspect exact schemas with client.describe().
One Result Contract
Compatible Tools return a consistent result shape, making previews, downloads, uploads and pipelines easier to build.
Reusable UI and Engine
Use Zavilo’s existing Tool UI where interaction is required, or call the same processing capability without UI.
Headless · Interactive · Embedded
One Tool. Three ways to integrate.
Choose the integration style that matches each workflow without changing the underlying Tool model.
Headless
Automate processing with client.run(). Best for background workflows and multi-step pipelines.
client.run()Interactive
Open the Zavilo Tool UI with caller-provided state, let the user edit, then receive the completed result.
client.open()Embedded
Mount a complete Tool experience inside your own page so users can select, process and download directly.
client.mount()Browser processing architecture
The engine comes to the browser. Your files stay there.
Zavilo delivers the processing engine and required runtime assets to the browser. Source files and generated result files are not sent to Zavilo servers; actual file processing runs in the user’s browser. Only the minimum control data required for SDK operation—such as authentication, Origin validation, Tool and Mode permissions, execution policy and usage accounting—is exchanged with Zavilo.
Processed in the browser, not uploaded to Zavilo for normal browser-based Tool execution.
Created and returned in the browser without being sent back to Zavilo.
Authentication, Origin, permissions, execution policy and usage data only.
Traffic & performance
Less waiting. Less file traffic.
Traditional file-processing services typically upload the source file to a processing server and download the result again. Zavilo removes that file round trip for browser-based Tools, which can significantly reduce transfer wait time and large-file network traffic.
Move the engine, not the files.
Traditional
FileUpload →Server→ DownloadResult
Zavilo
Engine → Browser
File→ Local processing →Result
Faster response
Avoid source upload and result download waits. The benefit becomes more noticeable as files get larger.
Less file traffic
Source and result binaries do not travel through Zavilo processing servers during normal browser-based execution.
Lower infrastructure load
Reduce the need for high-volume upload endpoints, processing servers, temporary file storage and result egress.
Local processing
Processing work is distributed to the user’s browser instead of concentrating file workloads on a central processing server.
+
Continuously expanding
New Tools, the same integration model.
Zavilo is not a fixed bundle. New image, document, media and developer Tools continue to be added while the SDK interface and Tool contract remain consistent.
Integrate Zavilo once, then adopt newly available Tools without redesigning your SDK architecture.
Start with one Tool. Expand when you need more.
Browse the live Tool Registry, inspect exact schemas, or open the integration examples and recipes to see complete workflows.