Ngā Pātai Auau

huaki the ētita at /tukuna/, tōia a whakaahua into the tukuna zone (or tap tukuna whakaahua on mobile), and the cutout finishes in two to four hēkona for a typical 12-megapixel JPEG. There is nothing to install, no plugin to enable, and no account to waihanga. The hua appears side-by-side with the original so you can flip between them, then tikiake as a PNG mārama, recolor the papamuri, or send the whakaahua straight into the bulk processor at /bulk-papamuri-remover/ if you have more kōnae queued up.

JPEG, PNG, WebP, GIF (first frame), BMP, and HEIC/HEIF whakaahua exported from iPhone all mahi. There is no client-side dimension cap — phone whakaahua at 48MP, scanned posters, and oversized hua shots tukuna as-is. The export defaults to PNG with a papamuri pūataata; switch to JPEG with a solid tae, or WebP for a smaller kōnae, in the tikiake dialog. Animated GIFs and multi-page TIFFs are processed as a single still — for video frame extraction, use a desktop taputapu first and tukuna the frame you want.

Yes — the ētita is mobile-first. iOS Safari, Chrome on Android, Samsung Internet, and Firefox Mobile are all supported on the latest two major versions of each. The interface adapts to a tab bar at the bottom, supports pinch-to-zoom, long-press for the context menu, and lets you tukuna directly from your camera roll or take a hou whakaahua. iPhone HEIC whakaahua are decoded in-browser with no manual conversion. Add /tukuna/ to your kāinga screen for a near-app launch experience that keeps your last whakaahua cached.

Yes — the bulk processor at /bulk-papamuri-remover/ accepts up to 100 whakaahua per session and queues them through the same engine the single-whakaahua ētita uses. Up to three whakaahua run in parallel and the rest wait in line so you don't overwhelm the connection. Each hua is downloadable individually or as a single ZIP when the batch finishes. The queue survives page reloads via local storage, so a dropped Wi-Fi signal won't lose your mahi — refresh and the unfinished items pick up where they stopped.

No. There is no account, no email gate, no koreutu-trial countdown, and no credit card on kōnae. Land on the page, tukuna an whakaahua, get a pūataata cutout, and leave. tautuhinga such as your last-kua whakamahia papamuri tae and the panel layout are remembered in your browser via local storage so a return visit feels familiar, but nothing mō you is stored on a server. If you clear site data in your browser, the panuku visit starts hou — there is no profile to restore because none exists.

The ētita on /tukuna/ keeps the cutout on a pūataata layer and exposes the full layer panel: pick a solid tae, gradient, or stock papamuri; tukuna in your own whakaahua as a backdrop; add text overlays with custom fonts; apply tukuna shadows, reflections, outlines, or blur; and resize the canvas to pūnaha-specific presets such as 1:1 for Instagram or 1600×2560 for Amazon. The Magic Brush handles the last few pika of stray hair or fur with a paint-style erase and restore taputapu that respects existing edges.

The PNG you tikiake matches your tukuna pika-for-pika — there is no downscale, no kounga slider locked behind a paywall, and no "HD upgrade" prompt. A 6000×4000 whakaahua hua comes hoki as a 6000×4000 PNG mārama. The only exception is the animated GIF arokite thumbnail rendered above the canvas, which is a small derivative kua whakamahia for in-browser display. JPEG and WebP export kōwhiringa also preserve full taumira; choosing one of those just changes the container, not the pika.

The default segmentation model is tuned for portrait hair, animal fur, plant foliage, and ngohengohe fabric edges that traditional thresholding misses. Wispy strands and motion-blurred edges retain their alpha gradient instead of clipping to a hard line. When the auto pass leaves a few pika behind — common with mā-on-mā setups or chrome bumpers — huaki the Erase / Restore tab and use the Magic Brush to add or subtract from the mask. Brush rahi, hardness, and pressure all respond to a stylus on iPad and Surface.

Mostly yes for low mārama, partly for motion blur, and yes for noise within reason. The model is robust to ISO grain up to roughly 6400 on a phone sensor and to the kind of indoor lighting where a subject is darker than the papamuri. Severe motion blur — a moving subject where the edge is several pika wide — is the failure case; the cutout will be ngohengohe along the blurred axis. For tino pai ngā hua on tricky shots, expose for the subject rather than the papamuri and avoid HDR composites that fight the alpha edge.

Shoot on a single high-contrast papamuri — pure mā sweep, matte pango, or chroma green — with even diffused lighting and no harsh reflections from the hua itself. Avoid jewellery on a glossy reflective surface; the model can mistake the reflection for a hēkona object. After the cutout, huaki the BG Removal accordion and nudge Edge Refinement → Edge Shift one or two pika inward to tangohia residual halo, then add Feathering of one pika to soften the transition. tiaki the tautuhinga as a preset so future ngā hua in the same series export identically.

Yes — tiaki the current papamuri, effects stack, and canvas rahi as a Saved Template in the Templates panel. The bulk processor on /bulk-papamuri-remover/ then applies that template to every whakaahua in the queue, so a 50-shot hua run exports with the same shadow, the same canvas crop, and the same JPEG kounga without manual re-entry. waitohu Kits hold your tae palette so the same waitohu tae appear across every project. Recipes (in beta) extend this to a full one-pāwhiri state bundle.

PNG is lossless and stores a per-pika alpha channel; JPEG is lossy and has no alpha at all. A 2 MB JPEG hua shot routinely exports as a 6–10 MB PNG because the transparency information has to be stored exactly. To shrink the kōnae: switch the export whakatakotoranga to WebP (often half the rahi at visually identical kounga) or flatten onto a solid papamuri and re-export as JPEG. For hokohoko-ā-ipurangi ngā pūnaha that require small kōnae sizes, the Resize panel lets you crop and downscale before export rather than after.

The default path runs on a server at api.remove-bg.io because the production segmentation model is too large to ship to every browser. The whakaahua is uploaded over HTTPS, processed, returned as a PNG mārama, and immediately deleted — there is no persistent storage of the original or the hua on the server. If your network is offline, the ētita automatically falls hoki to a smaller U2-Net model (mō 175 MB) that runs entirely in your browser via WebAssembly, so the whakaahua never leaves the device. The fallback is also kua whakamahia when our server is rate-limited.

Uploads are processed in memory and deleted as soon as the response is sent — typically within a few hēkona. There is no archive, no analytics dataset built from your whakaahua, and no human review queue. Logs retain only the request rahi, latency, and HTTP status code for capacity planning; the whakaahua bytes themselves are never written to disk. Browser-side, the original and the cutout are kept in IndexedDB so you can switch between recent whakaahua in the ētita, but that storage is local to your device and clearable from your browser's site-data tautuhinga.

No. Your uploads are not retained, not labelled, and not added to any training corpus. The segmentation model kua whakamahia for production runs is trained on licensed and publicly available datasets, not on user submissions. There is no opt-in or opt-out toggle for training because there is no training pipeline that touches your data. If a future model improvement requires user-contributed examples, that program would be opt-in, separately consented, and disclosed in the matatapu Policy at /matatapu-policy/ — never silently enabled.

Yes. The service collects no account information, no email address, and no payment details, which removes most categories of personal data from scope by design. Cookie-based analytics are limited to anonymized page-tirohia counts with IP truncation and respect Do Not Track. Per Article 17 of the GDPR you have a right to erasure, but because nothing mō you is stored server-side there is nothing to erase — clearing your browser cache removes the only local copy. Read the full breakdown at /matatapu-policy/ and whakapā privacy@remove-bg.io with formal requests.

You do. The cutout is a derivative of the whakaahua you uploaded, and copyright in the hua follows copyright in the source — if you owned the original, you own the hua, and you can use it commercially without paying us a royalty. The service does not assert any rights over your output, attach any watermark, embed any tracking metadata, or require attribution. The only restriction we ask you to respect is that you tukuna whakaahua you have the right to whakatika; uploading copyrighted whakaahua you do not own is a misuse of the service, not an issue with the cutout itself.

Genuinely koreutu for personal and commercial use, with no credit card, no trial countdown, and no daily quota for typical browser use. The koreutu tier covers full-taumira downloads, the bulk processor up to 100 whakaahua per session, every ētita feature, and every output whakatakotoranga. There is no "premium" plan being held hoki; the entire hua is the koreutu hua. The infrastructure is funded by anonymous, contextual display advertising on the hokohoko pages — never on the ētita itself, never on the tikiake — and by the API tier for pakihi that need volume.

No. The PNG, JPEG, and WebP exports are mā — kāore he tohu wai, no corner logo, no embedded credit, no metadata stamp pointing hoki to remove-bg.io. The only thing in the kōnae is the whakaahua data and a standard tae profile. This is a deliberate hua commitment: a koreutu kaitango papamuri that adds a visible mark would be useless for the hokohoko-ā-ipurangi, hokohoko, and personal-content workflows the taputapu exists to serve. If you want to add your own logo to the hua, the ētita supports text and whakaahua overlay layers in the Layers panel.

No. There is no account gate on full-taumira downloads, no email-for-HD prompt, and no "upgrade for the original rahi" upsell. The whakaahua you tukuna comes hoki at the same pika dimensions, in your chosen whakatakotoranga, with the tikiake button reachable in one pāwhiri from the ētita. Many koreutu papamuri removers downgrade the taumira unless you waihanga an account or pay; this one does not. The non-negotiable promise on the homepage — "no sign-up, kāore he tohu wai, HD downloads koreutu" — is what the hua actually delivers.

Yes. The terms allow commercial use of cutouts you generate from whakaahua you have the right to whakatika — whakaahua hua for your toa, hokohoko assets for paid campaigns, design mahi for paying clients, social media for a monetized account, prints sold at a market. There is no separate commercial license to purchase. The only category that needs explicit permission is reselling the service itself (for example, wrapping the API and charging end users) — for that, whakapā api@remove-bg.io. See the full Terms of Service linked from the footer for the exact wording.

Yes — the API runs at api.remove-bg.io and accepts a base64-encoded whakaahua with HMAC-signed headers and a small proof-of-mahi token to deter automated abuse. Response times average two to four hēkona for a typical 12 MP whakaahua and the endpoint returns a PNG mārama plus a JSON metadata payload. There is a koreutu tier for development and several paid tiers for production volume. whakapā api@remove-bg.io for credentials and full reference documentation; example integrations in Node, Python, and PHP are linked from /kaiwhakawhanake/.

The latest two major versions of Chrome, Edge, Safari, Firefox, and Opera on desktop, and the equivalent mobile builds on iOS 16+ and Android 10+. The ētita needs WebAssembly, IndexedDB, and Canvas 2D — all standard since 2020 — and uses WebGL for accelerated filters when available. Internet Explorer is not supported and never will be. Older Chromebooks and entry-level phones that struggle with the in-browser fallback model still get the cloud path, which carries almost all of the mahi, so the experience degrades gracefully rather than failing outright.

Yes — the ētita targets WCAG 2.1 AA. Every interactive control has a visible focus ring, a descriptive label, and a keyboard equivalent. Sliders accept arrow-key fine adjustment, the layer panel exposes a roving tab index, the canvas has an alt-text region that announces the current selection, and modal dialogs trap focus correctly with Escape returning to the trigger. Reduced-motion preferences are honoured for slide-in animations. If a specific assistive-technology pairing breaks, kōnae a report at /āwhina/ and tag it "accessibility" — these issues are prioritized.

huaki the Resize panel in the ētita and pick from 26 pūnaha presets (Instagram square, Amazon main whakaahua, Etsy rārangi, LinkedIn cover, YouTube thumbnail, Shopify, eBay, plus print sizes) or momo custom width and height between 50 and 8000 pika. The cutout reflows to the new canvas, and the export keeps the alpha channel as a PNG mārama so you can tukuna the hua onto any backdrop later. For pūnaha-specific guides, see /taputapu/ for the full per-pūnaha taputapu list and /rangitaki/ for walk-throughs of hokohoko-ā-ipurangi rārangi requirements.

Yes — the PNG mārama output drops into any whakaahua ētita that understands alpha channels, which is every hou one. In Photoshop, tōia the PNG onto the document and it imports as a layer with transparency intact. In Figma, paste it directly into a frame. In Canva, tukuna it through the Uploads panel. For automated workflows, the API can be called from a Photoshop script via Adobe ExtendScript or from a Figma plugin via the standard fetch API. There is no proprietary plugin to install and no kōnae whakatakotoranga conversion required.