Contact ImageToLine

Last updated: 2026-09-23

This page explains how to reach the ImageToLine team, what to include so your message is actionable, and how to solve the most common issues yourself in under a minute. The site is small and independent; every report genuinely shapes the next build.

What we want to hear about

Four categories cover almost everything we can act on.

Bugs. A tool that errors out, produces an empty result, freezes the tab, or renders something clearly broken (half a face, solid black blobs, a completely white image) is a bug. Include the details listed below and we will reproduce it against our test set.

Quality reports. Not wrong, just… off? If a photo converts into something usable-but-ugly — broken outlines, missing facial features, patchy shading — send us the context. Tell us which tool, which sliders you moved, and what the photo was like (soft portrait, busy background, low light). Quality reports drive most preset tuning.

Feature requests. Batch conversion, SVG export, new presets, new languages, print layouts — tell us what you would use most and why. Requests are prioritized by how often they are requested and how well they fit the local-processing architecture.

Translation corrections. The site is bilingual (English and German). If a German sentence reads awkwardly or a term is wrong, we fix it — language reports are the fastest kind to resolve.

What to include in a bug report

Five facts reproduce almost every issue:

1. The tool and the URL — for example, the photo to outline converter at /photo-to-outline.
2. Your browser and version — Chrome 129, Firefox 131, Safari 18, and so on, plus your operating system.
3. The image facts — format (JPG, PNG, WebP), approximate file size, and pixel dimensions. Do not send us the photo itself unless we ask; describing it is enough to start.
4. What you did — upload only, or which sliders you dragged and to what values.
5. What happened — the exact error text if one appeared, or a short description of the wrong output ("the outline of the dog was missing its back").

With those five, most reports are diagnosed the same day. Without them, the first reply is usually a request for exactly this list.

Self-service: fix it in under a minute

Most problems are not bugs — they are one of these five:

"Unsupported format" error. The tools accept JPG, PNG, and WebP. If your file is a HEIC (common on iPhones), a TIFF, a PDF, or an AVIF, convert it to JPG or PNG first — every phone gallery and most photo apps do this via Share or Export. Screenshots in exotic formats fall in the same bucket.

"Too large" error. The limit is 15 MB per file. A 48-megapixel phone photo in PNG can exceed it easily; exporting as JPG at quality 90 usually lands under 5 MB with no visible loss for line conversion.

"Too small" error. Inputs below roughly 128 pixels on the short edge are rejected because the line engine has too little to work with. Crop less aggressively or use the original file rather than a thumbnail.

The result is too sparse or too dense. That is what the sliders are for. Detail controls how many secondary lines survive, Line Thickness sets stroke weight, Clean Up removes small fragments, and Contrast stretches tones before processing. Small moves matter — try ±15 at a time. The preview re-renders as you drag.

The tab feels slow on a huge file. Exports up to 4096 pixels process in a few seconds on typical laptops; a max-size image on an older phone can take longer because everything happens on your device. Closing other heavy tabs helps; the browser tab doing the work is the machine doing the work.

Printing tips for coloring pages

If you turn picture into coloring page output and the print looks wrong, check three things: print at 100 percent scale (not "fit to page", which can soften lines), use Letter or A4 with margins, and prefer a laser printer or a high ink setting on inkjets so thin strokes stay solid. The PNG export keeps your original aspect ratio up to 4096 pixels, which is more than any home printer resolves.

Response expectations

We read everything. Bug reports usually get a first reply within two business days; quality and feature reports are batched weekly into the build queue; translation fixes often ship within a day because they are small. There is no support level to buy — the tools are free and so is the support, within the limits of a small team.

How feedback is handled

Reports enter a private triage list. Bugs are reproduced against the three public example photos (portrait, dog, building) plus an internal set of edge cases — noisy phone shots, snow scenes, high-ISO grain, screenshots. Reproducible bugs become engine tickets; non-reproducible ones get a follow-up question. Feature requests accumulate with a count of how many people asked; the roadmap on the about page reflects the current order.

Privacy note

Because processing is local, we never see the images you convert. If you later choose to email us a problematic photo, send only what you are comfortable sharing, and tell us in the message if it should not be kept — see the privacy policy for how correspondence is handled.

Stay current

Tool updates, new presets, and new pages are announced on the site itself; the "Updated" line under each tool's heading always shows the month of the last engine change. If you are building something with the tools — worksheets, stencils, coloring books — the terms of service confirm the outputs are entirely yours.

Browser support

The engine needs a browser with Web Worker and Canvas support: Chrome, Edge, Firefox, and Safari, desktop and mobile, in versions from roughly 2022 onward. Older browsers may load the page but fail silently inside the worker; if the preview never appears after an upload, first try a current browser, then report the issue with your browser version. No installation, extension, or app is ever required.