NormalMapGenerator.net

Contact Us

Useful reports include the browser, operating system, exact tool URL, source dimensions, reproducible steps, expected result, and actual result. Do not send confidential source textures through an unverified channel.

Configured contact email

Send reports to the selectable address below. Do not include confidential source assets unless a secure channel is agreed first.

[email protected]

Details that make a report reproducible

Browser and exact version
Operating system and device
Full tool URL and locale
Source dimensions and format
Steps and settings
Expected result
Actual result
Optional non-confidential screenshot
1

Report a technical problem

Begin with the exact page URL, browser version, operating system, image dimensions and format, followed by numbered steps from a fresh page load. Include the setting values that change the result, such as filter, strength, Y convention, edge mode, or output type. Describe what you expected and what appeared instead. A cropped, non-confidential screenshot is useful for layout, error-message, channel, or shading problems. If possible, say whether the sample image reproduces the issue; that separates an interface or calculation fault from characteristics of a private source asset.

2

Request a documentation or accessibility correction

For a factual correction, quote the page heading and explain which statement is inaccurate, ambiguous, or outdated. A link to current primary documentation is especially helpful for software import behavior that can change by version. Accessibility reports should name the input method—keyboard, touch, pointer, screen reader, zoom, reduced motion, or high contrast—and identify where the task becomes blocked. Translation feedback should include the locale and the intended technical meaning, not only a literal replacement, because terms such as tangent, normal, height, and convention have workflow-specific meanings.

3

Protect source assets when asking for help

Do not email unreleased textures, proprietary scans, client artwork, credentials, or personal data merely to demonstrate a defect. First reproduce the behavior with the built-in sample, a synthetic image, or a cropped substitute that carries no confidential information. If the problem truly depends on the original, ask the configured owner whether an appropriate transfer method exists and what retention applies before sending anything. The public browser tools do not upload selected source pixels to an application server, but sending a file separately by email would be a different data flow covered by the contact and privacy information.

Do not send confidential texture sources or material scans unless the owner confirms a secure transfer channel. A screenshot can usually show UI and rendering defects without exposing the original asset.