Pixelport

Pixelport is a desktop batch image-processing application for online sellers and content creators, shipped as macOS and Windows installers. The website carries only description, download and purchase; processing starts in the client.

The site describes its users as individual sellers and small shops that shoot or prepare their own product photos, a business use. No material addresses studios, agencies or enterprise procurement.

• Individual online sellers who shoot their own product photos
• Operators of shops with one to three people
• Makers and resellers listing handmade or second-hand goods
• No documented enterprise or agency purchasing

A seller takes the dozens or hundreds of photos from one shoot, removes the backgrounds, crops them to each marketplace size and exports files ready to upload. The site presents a single product drop as the main trigger.

The site describes the prior approach as editing image by image in a general editor, or sending photos to a retoucher. Community comments describe using an editor’s batch actions, which required a separate saved action per marketplace size.

Product proposition: take one shoot’s entire set of product photos to upload-ready state in a single operation. The site demonstrates this with before-and-after pairs and a "120 images, one export" example, without evidence of hours actually saved.

The download page lists macOS 13 or later and 64-bit Windows 10 or 11, with an English-only interface. No Linux build, Windows ARM build or additional interface language is documented, and no service region is stated.

Checked 16 September 2026: the site loads, and both the installer link and the purchase entry open. No shutdown or maintenance notice is posted, and the most recent downloadable build is dated 14 August 2026.

Core delivery is batch background removal, batch cropping to marketplace dimensions and bulk export. Saved presets, an export log and retry-on-failure are supporting capabilities. No account system, cloud storage or collaboration feature appears anywhere on the site.

The feature page accepts JPG, PNG and WEBP files individually or as a whole folder, up to 500 images per batch. HEIC is labelled experimental support, and no per-file size limit is stated.

Output is transparent-background PNG or white-background JPG, cropped to the chosen preset, written to a named subfolder with an export log. Site examples show 2000×2000 and 1200×1600; only those two examples’ format and dimensions are confirmed.

The core path runs: select source images → choose background removal and a size preset → check the first three previews → run the bulk export. Preview is local and free; credits are deducted at export, per image successfully processed.

1. 1User

   Select source images

   Drag a whole shoot folder into the window, or add files individually, up to 500 per batch.

2. 2User

   Choose processing and preset

   Enable background removal, then pick an output size preset and a background type, transparent or white.

3. 3Application

   Render the first three previews

   The preview renders locally and consumes no credits, so edges and cropping can be checked first.

4. 4User

   Run the bulk export

   Export to a chosen folder or ZIP with an export log; credits are deducted per image processed successfully.

Four kinds of page carry the overview, capability detail, pricing and download. The application’s own interface is visible only through site screenshots; no running build was captured, so interface order is read from those screenshots alone.

Homepage

Before-and-after pairs, three capability lines and a download button

Feature pages

One process each: description, samples, a limits list and the download entry

Pricing page

Three credit packs, per-credit price and the deduction rule

Download page

Installer links, system requirements and checksums

Processing requires downloading and installing the desktop client first. Background removal needs a connection and consumes credits, while cropping and export run locally and are not charged. The download page states that the granted credits need no account.

Help articles document only local folder import and export to a folder or ZIP, optionally with a CSV manifest. No API, platform connection or plugin is documented, and no marketplace back office integration is mentioned.

Payer and user are the same person: the seller buys a credit pack, and what is purchased is a number of background-removal operations. No company purchasing route or paying-on-behalf arrangement is documented.

Pay-as-you-go: one successful background removal costs one credit, while cropping and export are not charged. There is no subscription and no billing cycle; credits are bought outright and spent per operation, with a minimum purchase of 100 credits.

There are no plan tiers, only three credit packs named by size: Starter 100, Studio 500 and Bulk 2000. All three unlock identical capability and differ only in credit count and per-credit price.

• Starter 100
• Studio 500
• Bulk 2000

The pricing page lists three credit packs: Starter 100 at USD 9, Studio 500 at USD 39 and Bulk 2000 at USD 129, priced in US dollars with no statement about tax. No monthly or annual price exists.

First install grants 30 credits, and the pricing page states that purchased credits do not expire. A batch holds at most 500 images, and credits accumulate against a device identifier; whether they can be shared across machines is not stated.

First install grants 30 credits, and the download page states that no account and no card are required. When credits run out the app still crops and exports but stops removing backgrounds. There is no timed trial and no automatic charge is described.

The first charge arises when the 30 granted credits are exhausted and the user runs another background-removal export: the app reports insufficient credits and links to the pricing page. Cropping and export never trigger payment on their own.

Estimated site visits for August 2026 are 15,000, covering global desktop and mobile web, from a traffic model. The series peaks at 21,100 in April 2026 and has declined for four consecutive months since.

The confirmable milestones cluster in the first year: the first public build in November 2024, resize presets in March 2025, and a move from a one-off licence to credit billing in September 2025. After April 2026 the changelog holds only two entries, both bug fixes.

2024-11-08

Site launches with the first macOS build

2025-03-19

Marketplace size presets added

2025-06-02

Windows build added

2025-09-24

One-off licence replaced by credit billing

2026-04-22

Last feature release: bulk export rewritten

2026-05-30

Bug fixes

2026-08-14

Bug fixes, including HEIC import

The about page names a single founder who also handles support and writes the changelog. No other member, contractor or job posting is visible. Team size is recorded as one, on the company’s own statement, checked 16 September 2026.

Estimated monthly revenue is USD 1,800 for August 2026, a third-party modelled figure the company has not disclosed. Because credits are bought outright there is no contracted recurring revenue, so the figure indicates order of magnitude only.

Estimated visits fell from 16,000 in July 2026 to 15,000 in August 2026, a decrease of 1,000 or −6.25% month over month. This is the fourth consecutive monthly decline since May 2026, with both months on the same model and basis.

Three kinds of acquisition activity are observable: feature pages that catch organic search for specific processing needs, release posts on the founder’s personal account, and a small set of directory and community pages that refer traffic. No paid placement was found within the scope searched.

Organic search

Three feature pages and two help articles, an estimated 41% of visits in the window

Founder publishing

One social account, falling from two or three posts a month to zero or one after May 2026

Referral

46 referring root domains, mostly tool directories, flat since June 2026

Paid placement

No record observed in ad-library searches covering March to September 2026

The site footer links one account whose bio identifies it as the founder’s personal account, also used for product updates; no separate brand account exists. For any other publisher, the relationship to the product cannot be verified.