🔮 Universal Image Data Explorer Forge

60+ Converters | Binary ⇄ Hex ⇄ Pixel ⇄ Code

Support & Troubleshooting

Step-by-step help for converters, the revert engine, downloads, browser compatibility and performance before you contact the team.

🐛 Bug Reports 🛠️ Troubleshooting 📧 Email Support 📱 Browser Help

Technical Support Channels

Universal Image Data Explorer Forge is maintained by a small team. Because the tool is entirely client-side and offered free of charge, we do not provide paid support contracts, telephone helplines or guaranteed response-time SLAs. We do, however, read every email and prioritize issues that affect data accuracy, privacy, accessibility or browser compatibility.

Before You Contact Support

Many common issues are solved by a few simple checks. Please try these first:

  1. Refresh the page — press Ctrl+F5 (Windows) or Cmd+Shift+R (macOS) to force-reload and clear stale ES modules.
  2. Use a modern browser — Chrome 90+, Firefox 88+, Safari 15+ or Edge 90+.
  3. Check the System Logs panel — the green panel on the right of the dashboard often contains the exact error message.
  4. Verify your image size — files up to 8 MB are accepted. Larger files are rejected with a clear error.
  5. Confirm a converter is selected — the CONVERT button requires both a loaded image and a selected converter.
  6. Try a different image — this helps isolate whether the issue is with the file or with the tool.

Common Issues and Fixes

Converter produces no output when I press CONVERT

Cause: no image is loaded, or no converter is selected.
Fix: check the metadata panel on the right — it should show the image dimensions. Check the left sidebar — one converter button should be highlighted green. If nothing is selected, click any converter once and press CONVERT again.

The binary output looks like decimal numbers (170, 170, ...) instead of 0s and 1s

Cause: you selected Byte Array or Decimal, not Binary (bits).
Fix: in the left menu, expand group A. Binary / Low Level Data and click Binary (bits). The output should be a continuous stream of 0s and 1s. Byte Array and Decimal produce numeric outputs by design — they are different converters.

Revert shows "binary length mismatch"

Cause: the pasted bit stream is not exactly width × height × 8 bits long.
Fix: verify that you copied the entire output — some terminals truncate long strings when copying. Check the width and height inputs — they must match the original image dimensions. For a 100×100 image, the binary string must be exactly 80,000 characters.

Revert canvas stays blank after clicking Revert → Image

Cause: the byte count does not match width × height.
Fix: open the System Logs panel — it will tell you the expected count and the actual count. Adjust width/height to match your data, or check that your pasted array is complete.

Browser freezes when converting a large image to RGB Matrix or Emoji Art

Cause: matrix-style converters grow quadratically with image size. A 2000×2000 image produces four million integers per channel.
Fix: downsample the image in an external editor to 500×500 or smaller before uploading. The conversion algorithms are correct; the browser simply cannot render such large text outputs quickly.

File is rejected as "too large"

Cause: the file exceeds the 8 MB upload limit.
Fix: resize the image in any image editor or use an online compression tool. The 8 MB limit protects the browser from running out of memory during large matrix or SVG conversions.

Download button does nothing

Cause: downloads are locked until you register an email.
Fix: enter any valid email address in the Unlock Downloads box and click Register & Unlock. The email is stored only in your browser's localStorage and never transmitted.

Downloaded .bin file is empty

Cause: the .bin option is only meaningful after running the Binary converter, which populates the raw byte buffer.
Fix: first select Binary (bits), press CONVERT, and then choose the .bin download format. For other converters the .txt download works better.

Hash values differ from what another tool reports

Cause: the Forge hashes the canonical grayscale byte stream, not the original file bytes.
Fix: this is by design. To reproduce the Forge's hash in another tool, first extract the grayscale bytes with the Byte Array or Python Bytes converter and then run your hash function over that byte stream.

Colour-space values look different from Photoshop or OpenCV

Cause: the Forge assumes sRGB source, D65 white point and BT.601 coefficients. Photoshop and OpenCV may use different assumptions.
Fix: for approximate analysis the values are close enough. For colorimetric precision, use a dedicated colour-management library. See the Disclaimer for details.

Tool does not work offline after the first page load

Cause: the fonts or ES modules were not cached.
Fix: load the page while online, wait for it to fully render, then disconnect. Some browsers aggressively clear their cache — use a private window with disk caching enabled, or install the page as a Progressive Web App if your browser supports it.

Mobile layout is broken on a very small screen

Cause: an unsupported very narrow viewport (below 320 px).
Fix: the Forge supports devices from 320 px upward. Below that, the layout may overflow horizontally. Rotate to landscape if possible. Report the exact viewport width if you find a bug.

How to Write a Useful Bug Report

A useful bug report lets us reproduce the issue on the first attempt. Please include the following:

Please do not attach the original image if it contains confidential content. Instead, describe the pixel pattern — for example "a 100×100 image with a red square in the top-left corner" — and we can reconstruct a test case ourselves.

How to Request a Feature

Feature requests work best when they explain the use case. Compare these two examples:

Use-case-driven requests are prioritized because they help the largest number of users and integrate cleanly with the existing pipeline.

Security Disclosures

If you discover a security issue — for example, a way to make the tool leak image data over the network, a cross-site scripting injection through the revert textarea, or a way to exfiltrate the email list from localStorage — please email support@startknowledge.in privately before public disclosure. We will acknowledge the report within five working days and coordinate a fix.

Privacy reminder: Please do not send passwords, API keys, authentication tokens, private keys, payment-card numbers or other confidential credentials through ordinary email. If a technical problem can be reproduced without exposing sensitive information, describe the steps instead.

Response Time Expectations

The Forge is maintained by a small team. We aim to acknowledge every message within five working days. Bug fixes that affect data accuracy, privacy or accessibility are prioritized over cosmetic changes. Feature requests are reviewed monthly. Documentation corrections are usually published within two weeks. Please allow additional time during holidays and at the end of the calendar year.

Related Pages

Related StartKnowledge Projects

Email Support Back to Forge FAQ