40 questions about devices, browsers & languages.

Yes — Chrome 120+ is the primary target. All tools, including the heaviest (large PDFs, video compression in V2) work optimally on Chrome.

Yes — Firefox 120+ is fully supported. WebCodecs is slightly more limited than Chrome which can affect video tools (V2).

Yes — Safari 17+. File system access is more restrictive than Chrome, so dropping multiple files is slower; otherwise all tools work.

Yes — Edge 120+ is Chromium under the hood, identical experience to Chrome.

Yes — Brave is Chromium-based, identical to Chrome. Shields don't interfere.

Yes — Arc is Chromium-based with custom UI on top. All tools work identically.

Yes — Chromium-based, identical to Chrome.

No — IE is end-of-life. Use Edge instead.

Yes — Chromium-based, identical experience.

Yes — fully tested on macOS Sonoma + Ventura + Monterey. All browsers.

Yes — Windows 10 + Windows 11, all major browsers.

Yes — tested on Ubuntu 22.04+ and Fedora 38+. Chrome / Firefox / Chromium-based browsers all work.

Yes — ChromeOS is well-supported. Heavy in-browser tools may be slower depending on Chromebook hardware spec.

Yes — iOS Safari 17+. The UI adapts to phone screens. PWA install ('Add to Home Screen') gives an app-like experience.

Yes — Android Chrome 120+. UI adapts to phone + tablet sizes. PWA install support coming V2.

Yes — full iPad Safari 17+ support. Large screen makes most tools comfortable on iPad — even for video work.

Yes — Chrome on Android tablets is well-supported.

Quest Browser is Chromium-based; tools work but the workflow is awkward in VR. Not a primary target — desktop / mobile take priority.

Most tools degrade gracefully — you'll see error messages where modern APIs are unavailable (WebCodecs, Canvas, etc.). Minimum: Chrome 100, Firefox 100, Safari 16. Older browsers should upgrade for security anyway.

Browser-side tools (PDF Compress, etc.) work once the page is loaded. AI tools need network for the API call; they may time out on very slow connections (>30s).

Partially — browser-side tools work once the page is loaded. AI tools need network access. Full offline mode (PWA + service worker) ships V2.

Yes — every interactive element has ARIA labels, semantic HTML, and visible focus rings. WCAG 2.1 AA compliant.

Yes — every interactive element is keyboard-reachable with visible focus indicators.

Yes — system prefers-contrast: more is honoured. We're also OS dark/light mode aware via prefers-color-scheme.

Yes — Cmd/Ctrl+= or Cmd/Ctrl+- works as expected. We're tested up to 200% zoom without layout breaking.

Content yes (anything you paste in RTL is preserved). UI direction follows your browser locale; full RTL UI mirroring ships V2 alongside the localisation effort.

Stripe Checkout opens in a new tab — make sure popups are allowed for apexkit.pro. Otherwise the app is single-page and popup-free.

Apexkit doesn't serve ads, so most blockers don't interact. The exception: Plausible analytics is sometimes blocked (which is fine — we lose anonymous analytics, you don't lose functionality).

Generally no — Apexkit doesn't geo-restrict (any region works). VPN-routed traffic may add latency on AI tools; otherwise no impact.

Yes — for the main app. Stripe Checkout blocks Tor by default for fraud reasons; you'll need to disable Tor (or use a different exit) to subscribe. Free tier works on Tor without issue.

No — Supabase Auth uses cookies for session management. Cookies must be enabled at least for apexkit.pro.

No — Apexkit is a single-page React app; JavaScript is required. Marketing pages (homepage, /tools, /blog, /pricing) render server-side so they're partially viewable without JS.

Optimised for 1280×800 and up. Smaller (1024×768) works but feels cramped. Larger (1440×900, 1920×1080) is ideal.

Both — drag and drop work on touchscreens; hover-only UX (rare in our design) is replicated via taps where it matters.

Sign-in works (Supabase cookies are session-only in private mode). Some tools that need filesystem access may behave inconsistently — best on a regular window.

Yes — UI works with stylus input for sign-in, navigation, drag-and-drop. PDF annotation via stylus ships V2.

Tool outputs preserve input language by default. UI is en-GB only at launch (localisation in V2). Translate tool explicitly handles target language selection.

Yes — all dates render in your browser's local time zone via Intl.DateTimeFormat. Billing dates from Stripe reflect Stripe's UTC + your locale.

Most pre-2001 PDFs work, though pdf-lib occasionally throws on edge cases. Workaround: open the old PDF in Preview / Adobe and save a copy — that normalises it.

API responses include CORS headers for same-origin only. Cross-origin from your own frontend: use server-side request with your API key (don't expose key in frontend code anyway).