🔮 Universal Image Data Explorer Forge

60+ Converters | Binary ⇄ Hex ⇄ Pixel ⇄ Code

Contact Universal Image Data Explorer Forge

Reach the developer team for bug reports, feature requests, documentation corrections and partnership enquiries about the free browser-based image-to-data toolkit.

📧 Email Support 🐛 Bug Reports 💡 Feature Requests 🤝 Partnerships

Contact the Forge Team

Universal Image Data Explorer Forge is maintained by a small, focused team of developers and researchers working under the StartKnowledge ecosystem. Because the Forge is entirely client-side and offered free of charge, we do not provide paid support contracts, SLA-backed response times or telephone helplines. However, we do read every message we receive, and we prioritize issues that affect data accuracy, privacy, accessibility or browser compatibility. If a converter produces incorrect output, or if the Revert engine fails to reconstruct an image, that is treated as a high-priority bug.

This page explains which email address to use for which type of enquiry, what information to include so that we can reproduce your issue quickly, and what you can expect in terms of response time. Following the guidelines below will help you get a faster and more useful reply.

Which Email Address Should I Use?

The StartKnowledge ecosystem uses three separate email addresses for different purposes. Choosing the right one helps route your message to the correct person.

What to Include in a Bug Report

A useful bug report contains enough context for the team to reproduce the issue on the first attempt. Please include the following details:

Please do not attach the original image if it contains confidential or personal information. 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.

What to Include in a Feature Request

Feature requests work best when they explain the use case rather than just naming a format. Compare these two examples:

The second request tells us exactly who benefits, what the technical constraint is, and how the feature should behave. Use-case-driven requests are prioritized because they help the largest number of users and integrate cleanly with the existing pipeline.

What to Include in a Documentation Correction

If a page in the Documentation, a description in the FAQ, or an (i) icon tooltip contains an error, please tell us the URL of the page, the exact sentence that is wrong, and what the correct statement should be. Documentation fixes are usually published within two weeks because they are low-risk changes.

What to Include in a Security Disclosure

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 addresses stored in localStorage — please email us privately at support@startknowledge.in before public disclosure. We will acknowledge the report within five working days, attempt to reproduce the issue, and coordinate a fix. If you wish, we will credit you in the Changelog when the fix ships.

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.

Before You Contact Us

Many common questions are already answered on other pages. To save time, please check the following resources first:

Partnership and Integration Enquiries

If you represent a company, university, research lab or non-profit interested in embedding the Forge inside your own product, using the conversion algorithms in a commercial application, or sponsoring development of a specific format, please email contact@startknowledge.in with a short description of your use case. The Forge is free for personal, educational and commercial use — attribution is appreciated but not required. We do not currently offer white-labelling or dedicated enterprise builds.

Reporting Bugs on StartKnowledge Projects

The Forge is part of a larger family of projects maintained under the StartKnowledge umbrella. If your issue is actually about one of these sibling projects rather than the Forge itself, please contact the corresponding team or use the relevant project's own contact page:

About the Forge (Quick Recap)

Universal Image Data Explorer Forge is a free, browser-native developer toolkit that converts any raster image into more than sixty machine-readable formats — binary bits, hexadecimal, octal, byte arrays, Base64, Base32, Base85, RGB/RGBA/HSL/HSV/CMYK/YUV/LAB matrices, C/C++/Python/Java/Go/Rust/JavaScript/PHP/Swift/Kotlin source arrays, ASCII/Braille/Block/Emoji art, Pixel Grid, Heatmap, MD5/SHA1/SHA256 hashes, CRC32, Run Length Encoding, Delta encoding, NumPy arrays, TensorFlow tensors, CSV pixel data, Pandas DataFrames, Feature Vectors, SVG traces, CSS Data URIs and Canvas ImageData — and reverses any of those representations back into a pixel-perfect image. All processing happens locally in your browser using the Canvas API and Web Crypto API. No uploads. No tracking of image content. No account required. For more detail see the About page.

Related Pages

Email Support Back to Forge Read FAQ