Frequently asked questions

For Lumli’s currently available image, PDF, color, and QR workflows, the selected file is read and processed inside your browser on your device. It does not need to be uploaded to a cloud editing service for the core operation.

Lumli does not intentionally store the files you use with its local tools on Lumli servers. A temporary handoff, preview, settings, or result may be kept in browser storage on your own device so the workflow can continue between pages or sessions.

Your browser may keep temporary file data, previews, theme preferences, app assets, workers, and AI model files in localStorage, IndexedDB, localforage, or its cache. This storage stays under your browser and device controls.

Clear site data for lumli.io in your browser settings. This can remove local storage, IndexedDB entries, cached app files, and the installed PWA data. Downloaded output files must be deleted separately from your device.

Local processing avoids the routine upload step used by many online editors. Keeping the original file on your device reduces the number of systems that need access to it and removes cloud upload and server-storage stages from the core workflow.

No web application can promise absolute security. Local processing reduces avoidable data transfer, but your browser, device, extensions, operating system, network, and any external links still affect your overall security. Keep them updated and use a trusted device for sensitive work.

The local tools are designed to reduce exposure and can be useful for private workflows. You are still responsible for checking your organization’s security, legal, and compliance requirements before processing confidential, regulated, or client material.

Lumli’s currently available tools do not require an account, and the app does not use advertising cookies. The browser may still store technical cache and preferences needed for the app experience.

No. Lumli works directly in a modern desktop or mobile browser. Installing it as a progressive web app is optional and only provides quicker access and a more app-like experience.

Supported local features can continue working offline after the required page, app assets, workers, and model files have loaded and been cached. A first visit, uncached resources, updates, and external destinations still require a connection.

Support depends on the tool. Across Lumli, common inputs include PNG, JPG/JPEG, WebP, AVIF, HEIC, SVG, and PDF. Each tool page lists the formats and export options available for that workflow.

There is no single server upload limit for local tools. Practical limits depend on your device memory, browser, file complexity, and operation. Smaller files generally process faster and more reliably, especially on mobile devices.

You retain responsibility for and any rights you hold in your input files and generated outputs. Only process material you are authorized to use, and review Lumli’s Terms of Use for the full conditions.

Lumli is designed for creators, designers, developers, photographers, students, remote workers, small teams, and anyone who wants quick image and PDF utilities without an account or a routine cloud upload.

Yes. The tools are designed for focused tasks such as compressing an image, converting a format, preparing a PDF, removing a background, extracting colors, or creating a QR code without a complicated editor.

Most computation happens on the user’s device, which reduces ongoing server-processing costs. That makes it easier for Lumli to offer its everyday browser tools without accounts, watermarks, or usage subscriptions.