Image and video decision

Fotoperfil

A competent technical user can reproduce the core functionality (client-side background removal, enhancements, templates and export) in about a week; the vendor’s hosted free UX and scale are what you'd be foregoing.

Visit website

Built by Jon Kraayenbrink, who ships 7 products in this index

You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$50one-off30 h to build

$50/mo3 h/mo upkeep

No published price to break even against.

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Fotoperfil alternatives, with the arithmetic →

What a replacement has to do

  • Upload a selfie, remove background, apply auto-enhancements and a chosen template, edit, then download the finished profile photo.

What it still won’t have

  • The site’s zero-registration, free hosted UX and branding
  • Any proprietary server-side models or optimizations the vendor may use
  • Polish, A/B tested templates and community trust/traffic

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Fotoperfil does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a single-page web app (React) that runs entirely client-side for creating profile photos. Stack: React + Vite, TensorFlow.js or ONNX.js for in-browser person segmentation, a small image-processing pipeline (canvas/WebGL) for auto-enhance (exposure/contrast/sharpness), and a React UI for template selection and cropping (use react-avatar-editor). Scope in-scope: image upload/validation, client-side background removal, auto-enhance pipeline, template/background compositing, in-browser editor (scale/position/crop) and exporting downloadable JPG/PNG in presets. Out of scope: server-side storage, user accounts, analytics dashboard, and paid billing. Include error handling for unsupported formats and large files, unit tests for core image functions, and end-to-end tests for the create-download flow.
How we checked3 sources · 3/3 runs agreed · evidence score 90

How the score was reached

  • Build verdict base78
  • An open-source build was found+5
  • 3 cited sources+3
  • 3/3 assessment runs agreed+4
  • Evidence score90

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded