File processing
For the browser-based converters currently available, selected files are processed on your device. The live Image, Data, Archive, and Subtitle converters do not require supported source-file contents to be uploaded to a ConvertAnyFile conversion server.
Files and generated outputs can exist in browser memory while the page is open. Image conversion can use browser memory and WebAssembly resources; structured-data and subtitle conversion use browser workers; Archive conversion parses, decompresses, validates, and repackages supported containers in a worker. Closing or refreshing the page ends that working session. ConvertAnyFile does not provide cloud project storage for these local conversions.
For 7Z and RAR input, the Archive worker lazy-loads a same-origin static WebAssembly decoder when needed. Downloading that application runtime is a normal website asset request; the source archive itself is not sent with that request.
Image editing tools
Supported Image Tools also work locally in the browser. When you use tools such as visible-logo or watermark editing, the browser can decode selected images, keep previews and masks in memory, repair selected pixels in a local worker, encode new image files, and package multiple successful outputs into a ZIP without sending the selected image contents to a ConvertAnyFile editing server.
Batch state, mask coordinates, previews, repaired output blobs, and ZIP data can remain in browser memory for the current page session. Clearing the batch, refreshing, or closing the page removes that working session from the application; ConvertAnyFile does not provide cloud storage or cross-device history for these local editing jobs.
Accounts
The current converters, including Subtitle Converter, and Image Tools do not require an account, profile, or sign-in to process supported files. Because there is no processing account, the current workflow also does not provide cloud history or cross-device file storage.
Technical requests
Like other websites, the hosting and CDN layers may receive standard network request information needed to deliver pages and static assets, such as an IP address, user agent, requested URL, and timing information. Those delivery requests are separate from the contents of files processed locally by the converters and Image Tools.
Browser caching may store website assets such as JavaScript or WebAssembly locally so the application can load efficiently. Those cached application assets are not your converted or edited file library.
Analytics and advertising
ConvertAnyFile uses Google Analytics to understand aggregate website usage, such as page visits, traffic sources, browser or device information, approximate geographic information, and interactions with the site. Google Analytics may use cookies or similar technologies and may receive standard request and device information when its analytics script loads.
The ConvertAnyFile integration does not intentionally send the contents of files you select for conversion or editing, generated file contents, local masks, or your local outputs to Google Analytics. Analytics measurement is separate from the browser-based file-processing workflow.
ConvertAnyFile does not currently describe advertising services as active on this site. If advertising, personalized advertising, additional third-party tracking, or a consent-management platform is introduced, this policy and any required consent controls should be updated accordingly.
Security and limitations
Browser-based processing reduces the need to transmit file contents to a conversion or editing backend, but no website can promise absolute security. Keep backups of important originals and do not treat a converted or edited output as the only copy of an important file.
Extensions, browser software, operating-system features, or other programs on a device are outside the direct control of ConvertAnyFile. Users should keep their browsers and systems up to date and use trusted devices for sensitive work.
Changes
This policy may change as ConvertAnyFile adds features or external services. Material changes should be reflected on this page before or when those features are introduced so the published policy continues to match the product.