Frequently Asked Questions

Save your slider values (contrast, brightness, highlights, shadows, grain) with the project. Reusing the same values on similar lighting gives consistent black and white output.

Use `/batch-black-and-white-converter` when you need one baseline look across many photos. It is useful for galleries, catalog images, and first-pass client previews.

Cull and color-correct in Lightroom or Capture One first, then export high-quality JPEG/TIFF files and convert in BWConverter. Do final spot adjustments only on selected keepers.

The hosted interface is tuned for files up to 10 MB for smoother browser performance. Very large frames may still work, but available RAM becomes the practical limit.

No. Output keeps the original width and height. If you need smaller files, lower quality/compression at export.

For standard conversion, BWConverter supports common image formats such as JPG, PNG, and WebP. The logo converter also supports SVG input and preserves transparency.

Image pixels are processed locally in your browser. Optional analytics can collect anonymous usage events like page views; details are listed on `/privacy`.

Use `/privacy` and `/about` as policy references, then capture a browser network log during conversion to show there are no image upload requests.

Yes. Once assets are available locally, conversion can run without sending files to external APIs.

High-resolution images can exhaust browser memory. Try smaller batches, close extra tabs, or export a lighter intermediate file before conversion.

Use JPG/WebP with lower quality settings and verify output size before delivery. PNG exports are usually larger for photo content.

Visit `/examples` to compare before/after results and inspect style choices for portraits, newborn sessions, and street scenes.

Yes. You can reuse worker-based processing in a custom frontend setup. This is useful if you need black and white conversion inside an internal CMS.

Yes. Create a preset object with your preferred slider values and store it in local storage or your own settings layer.

There is no public hosted API endpoint. Batch processing is currently delivered through the web UI and browser worker architecture.