PixelOkay Help Center

PixelOkay offers focused browser utilities and longer editing or creative workspaces for images, PDFs, video, audio, documents, design, development, data and more.

The current platform does not require a PixelOkay cloud project account, and tools are currently free to access. Individual tool requirements and available features are shown on their pages.

A recent desktop version of Chrome, Edge or another supported modern browser is generally a good starting point. WebGPU, WebAssembly, codecs, microphone or camera access may differ. Consult the specific tool page.

Some tools need a secure HTTP(S) context, correct relative paths, modules or Workers and will not work correctly from file://. Use the deployed https://pixelokay.com route or a proper local development server. This is separate from uploading files for processing.

PixelOkay does not currently operate a server to receive local files for processing or a cloud project-sync backend. Normal file-editing workflows process selections in your browser. Features that intentionally call third-party endpoints are a separate case; read their tool-specific notices.

Yes, to load the website and optional libraries, fonts, AI models and other assets. API-test and public-link-import features may also contact an endpoint or import service when activated. Network requests are not the same as automatically uploading your local documents.

No. PixelOkay currently does not display ads. If advertising is introduced later, the Privacy Policy and any required choices will be updated.

When supported, they may be kept in your browser’s local storage, IndexedDB or related storage. For example, some document, spreadsheet and presentation editors offer local recovery drafts when autosave is enabled. They are not cloud-synced by that feature.

Use the relevant workspace’s clear or delete function where present. Browser site-data controls can also remove caches and saved drafts for pixelokay.com, but may erase other workspaces’ recovery files, settings and downloaded models. Export and back up first.

The PixelOkay on-device AI tools are designed to run their AI processing in your browser without a paid inference API. Model weights may download from an external host, and specific URL-import or network tools may still contact external services. Review the exact tool notices.

On-device AI needs model files on your device. Downloads can be large and may be cached for reuse. Where a download is needed, the tool should request explicit permission rather than silently downloading a model at entry.

AI performance depends on model size, free RAM, GPU/WebGPU support and browser storage quota. Try a smaller model, close memory-heavy tabs, or use the non-AI workflow when available. A slow first inference does not necessarily mean the page is frozen.

Some AI tools provide a cache-inspection and Delete All option. This can remove compatible cached models used by other PixelOkay tools on the same origin. Save projects first; deleting model caches may require downloading the models again.

For tools that offer a non-AI workflow, core editing and export should remain usable without loading a model. Some specialized AI-only tasks may not have an equivalent non-AI result; check the tool page.

Browser media and document export depends on supported codecs, fonts, layouts, frame timing and other factors. Inspect the exported file in a separate player or viewer and confirm its length, content and audio tracks where applicable.

Check available RAM, device storage and supported browser codecs. Retry with a smaller sample or lower output settings if the tool offers them. Save intermediate work and close unnecessary tabs.

There is no PixelOkay cloud backup for local projects. If browser storage has been cleared and you have no project export or other copy, recovery may not be possible.

Browsers can clear or evict site data, and private mode or storage-cleanup actions may remove caches. Do not treat browser storage as a long-term archive.

Those features require browser permission to capture data on your device. You can deny access, stop sharing, or change permissions in browser site settings. Recording features should describe what they capture and export.

PixelOkay may use client-side integrity or debugging-abuse checks. Browser extensions, window layouts or legitimate developer workflows can trigger false positives. Use the official HTTPS site, refresh once, and report a persistent warning to support. No warning should imply that merely opening DevTools is unlawful.

Some guarded workflows may route repeated warning cases to the Help Center after a warning. This should not automatically delete projects or block users from reading the policy pages. If it happens unexpectedly, please report the browser, page URL and warning text.

Email support@pixelokay.com with the tool name, URL, browser/OS, exact error and steps to reproduce. Do not include passwords, confidential files or private conversation text.

See the Privacy Policy, Terms of Service and Disclaimer linked at the bottom of this page. Tool-specific limitations are described on each workspace page.