Nā Nīnau Pinepine

wehe the mea hoʻoponopono at /hoʻouka/, kauō a kiʻi into the hāʻule zone (or tap hoʻouka kiʻi on mobile), and the cutout finishes in two to four nā kekona for a typical 12-megapixel JPEG. There is nothing to install, no plugin to enable, and no account to hana. The huaʻina appears side-by-side with the original so you can flip between them, then hoʻoiho as a PNG ʻāʻā, recolor the kua, or send the kiʻi straight into the bulk processor at /bulk-kua-remover/ if you have more nā faila queued up.

JPEG, PNG, WebP, GIF (first frame), BMP, and HEIC/HEIF nā kiʻi exported from iPhone all hana. There is no client-side dimension cap — phone nā kiʻi at 48MP, scanned posters, and oversized hua shots hoʻouka as-is. The export defaults to PNG with a kua ʻāʻā; switch to JPEG with a solid kala, or WebP for a smaller faila, in the hoʻoiho dialog. Animated GIFs and multi-page TIFFs are processed as a single still — for video frame extraction, use a desktop mea hana first and hoʻouka the frame you want.

Yes — the mea hoʻoponopono 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 hoʻouka directly from your camera roll or take a hou kiʻi. iPhone HEIC nā kiʻi are decoded in-browser with no manual conversion. Add /hoʻouka/ to your home screen for a near-app launch experience that keeps your last kiʻi cached.

Yes — the bulk processor at /bulk-kua-remover/ accepts up to 100 nā kiʻi per session and queues them through the same engine the single-kiʻi mea hoʻoponopono uses. Up to three nā kiʻi run in parallel and the rest wait in line so you don't overwhelm the connection. Each huaʻina 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 hana — refresh and the unfinished items pick up where they stopped.

No. There is no account, no email gate, no manuahi-trial countdown, and no credit card on faila. Land on the page, hāʻule an kiʻi, get a ʻāʻā cutout, and leave. hoʻonohonoho such as your last-ua hoʻohana kua kala and the panel layout are remembered in your browser via local storage so a return visit feels familiar, but nothing e pili ana you is stored on a server. If you clear site data in your browser, the aʻe visit starts hou — there is no profile to restore because none exists.

The mea hoʻoponopono on /hoʻouka/ keeps the cutout on a ʻāʻā layer and exposes the full layer panel: pick a solid kala, gradient, or stock kua; hāʻule in your own kiʻi as a backdrop; add text overlays with custom fonts; apply hāʻule shadows, reflections, outlines, or blur; and resize the canvas to pūnaewele-specific presets such as 1:1 for Instagram or 1600×2560 for Amazon. The Magic Brush handles the last few nā kiko of stray hair or fur with a paint-style erase and restore mea hana that respects existing edges.

The PNG you hoʻoiho matches your hoʻouka kiko-for-kiko — there is no downscale, no maikaʻi slider locked behind a paywall, and no "HD upgrade" prompt. A 6000×4000 kiʻi hua comes hoʻi as a 6000×4000 PNG ʻāʻā. The only exception is the animated GIF nānā mua thumbnail rendered above the canvas, which is a small derivative ua hoʻohana for in-browser display. JPEG and WebP export nā koho also preserve full hoʻonā; choosing one of those just changes the container, not the nā kiko.

The default segmentation model is tuned for portrait hair, animal fur, plant foliage, and palupalu 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 nā kiko behind — common with keʻokeʻo-on-keʻokeʻo setups or chrome bumpers — wehe the Erase / Restore tab and use the Magic Brush to add or subtract from the mask. Brush nui, hardness, and pressure all respond to a stylus on iPad and Surface.

Mostly yes for low mālamalama, 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 kua. Severe motion blur — a moving subject where the edge is several nā kiko wide — is the failure case; the cutout will be palupalu along the blurred axis. For ʻoi loa nā huaʻina on tricky shots, expose for the subject rather than the kua and avoid HDR composites that fight the alpha edge.

Shoot on a single high-contrast kua — pure keʻokeʻo sweep, matte ʻeleʻele, 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 kekona object. After the cutout, wehe the BG Removal accordion and nudge Edge Refinement → Edge Shift one or two nā kiko inward to wehe residual halo, then add Feathering of one kiko to soften the transition. mālama the hoʻonohonoho as a preset so future nā hua in the same series export identically.

Yes — mālama the current kua, effects stack, and canvas nui as a Saved Template in the Templates panel. The bulk processor on /bulk-kua-remover/ then applies that template to every kiʻi in the queue, so a 50-shot hua run exports with the same shadow, the same canvas crop, and the same JPEG maikaʻi without manual re-entry. hōʻailona Kits hold your kala palette so the same hōʻailona nā kala appear across every project. Recipes (in beta) extend this to a full one-kaoʻo state bundle.

PNG is lossless and stores a per-kiko 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 faila: switch the export ʻano to WebP (often half the nui at visually identical maikaʻi) or flatten onto a solid kua and re-export as JPEG. For kālepa pūnaewele nā pūnaewele that require small faila 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 kiʻi is uploaded over HTTPS, processed, returned as a PNG ʻāʻā, and immediately deleted — there is no persistent storage of the original or the huaʻina on the server. If your network is offline, the mea hoʻoponopono automatically falls hoʻi to a smaller U2-Net model (e pili ana 175 MB) that runs entirely in your browser via WebAssembly, so the kiʻi never leaves the device. The fallback is also ua hoʻohana when our server is rate-limited.

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

No. Your uploads are not retained, not labelled, and not added to any training corpus. The segmentation model ua hoʻohana 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 pilikino Policy at /pilikino-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-nānā counts with IP truncation and respect Do Not Track. Per Article 17 of the GDPR you have a right to erasure, but because nothing e pili ana you is stored server-side there is nothing to erase — clearing your browser cache removes the only local copy. Read the full breakdown at /pilikino-policy/ and hoʻopili privacy@remove-bg.io with formal requests.

You do. The cutout is a derivative of the kiʻi you uploaded, and copyright in the huaʻina follows copyright in the source — if you owned the original, you own the huaʻina, 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 hoʻouka nā kiʻi you have the right to hoʻoponopono; uploading copyrighted nā kiʻi you do not own is a misuse of the service, not an issue with the cutout itself.

Genuinely manuahi for personal and commercial use, with no credit card, no trial countdown, and no daily quota for typical browser use. The manuahi tier covers full-hoʻonā downloads, the bulk processor up to 100 nā kiʻi per session, every mea hoʻoponopono feature, and every output ʻano. There is no "premium" plan being held hoʻi; the entire hua is the manuahi hua. The infrastructure is funded by anonymous, contextual display advertising on the hoʻolaha pages — never on the mea hoʻoponopono itself, never on the hoʻoiho — and by the API tier for nā ʻoihana that need volume.

No. The PNG, JPEG, and WebP exports are maʻemaʻe — ʻaʻohe hōʻailona wai, no corner logo, no embedded credit, no metadata stamp pointing hoʻi to remove-bg.io. The only thing in the faila is the kiʻi data and a standard kala profile. This is a deliberate hua commitment: a manuahi mea wehe kua that adds a visible mark would be useless for the kālepa pūnaewele, hoʻolaha, and personal-content workflows the mea hana exists to serve. If you want to add your own logo to the huaʻina, the mea hoʻoponopono supports text and kiʻi overlay layers in the Layers panel.

No. There is no account gate on full-hoʻonā downloads, no email-for-HD prompt, and no "upgrade for the original nui" upsell. The kiʻi you hoʻouka comes hoʻi at the same kiko dimensions, in your chosen ʻano, with the hoʻoiho button reachable in one kaoʻo from the mea hoʻoponopono. Many manuahi kua removers downgrade the hoʻonā unless you hana an account or pay; this one does not. The non-negotiable promise on the homepage — "no sign-up, ʻaʻohe hōʻailona wai, HD downloads manuahi" — is what the hua actually delivers.

Yes. The terms allow commercial use of cutouts you generate from nā kiʻi you have the right to hoʻoponopono — paʻi kiʻi hua for your hale, hoʻolaha assets for paid campaigns, design hana 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, hoʻopili 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 kiʻi with HMAC-signed headers and a small proof-of-hana token to deter automated abuse. Response times average two to four nā kekona for a typical 12 MP kiʻi and the endpoint returns a PNG ʻāʻā plus a JSON metadata payload. There is a manuahi tier for development and several paid tiers for production volume. hoʻopili api@remove-bg.io for credentials and full reference documentation; example integrations in Node, Python, and PHP are linked from /nā mea hoʻomohala/.

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 mea hoʻoponopono 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 hana, so the experience degrades gracefully rather than failing outright.

Yes — the mea hoʻoponopono 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, faila a report at /kōkua/ and tag it "accessibility" — these issues are prioritized.

wehe the Resize panel in the mea hoʻoponopono and pick from 26 pūnaewele presets (Instagram square, Amazon main kiʻi, Etsy papa kuhikuhi, LinkedIn cover, YouTube thumbnail, Shopify, eBay, plus print sizes) or ʻano custom width and height between 50 and 8000 nā kiko. The cutout reflows to the new canvas, and the export keeps the alpha channel as a PNG ʻāʻā so you can hāʻule the huaʻina onto any backdrop later. For pūnaewele-specific guides, see /nā mea hana/ for the full per-pūnaewele mea hana list and /moʻolelo/ for walk-throughs of kālepa pūnaewele papa kuhikuhi requirements.

Yes — the PNG ʻāʻā output drops into any kiʻi mea hoʻoponopono that understands alpha channels, which is every hou one. In Photoshop, kauō the PNG onto the document and it imports as a layer with transparency intact. In Figma, paste it directly into a frame. In Canva, hoʻouka 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 faila ʻano conversion required.