Overview
ReportMedic is a browser-based diagnostics suite built for analysts, data teams, operations professionals, and anyone who works with reports, exports, and data files on a daily basis. The platform provides a curated collection of precision tools designed to solve the specific, often tedious problems that arise when working with real-world reporting workflows: format mismatches, column name inconsistencies, PDF extraction headaches, export corruption, data quality gaps, and version comparison.
Every tool on ReportMedic executes locally in your web browser using standard web APIs — File, FileReader, Blob, Canvas, WebAssembly, and related technologies. Your files are read into memory within your browser's sandboxed environment. No data is transmitted to a ReportMedic server as part of ordinary tool use. You load, process, review, and download — entirely on your device.
This architecture is not just a privacy feature — it is also a performance feature. Processing happens at the speed of your local CPU and memory, without round-trip latency to a remote server, without queue times, and without throttling based on a server-side resource budget. Large files that would time out on a remote API process immediately on modern hardware.
The documentation on this page is the primary technical reference for the platform. It covers tool categories, individual tool behaviour, the privacy and security model, browser compatibility, file size guidance, troubleshooting, and answers to frequently asked questions.
How It Works
Understanding the technical architecture helps you use ReportMedic with confidence and make informed decisions about what you load into each tool.
In-Browser Execution
When you navigate to a tool page, the browser downloads the tool's HTML, CSS, and JavaScript. That JavaScript contains all the logic needed to perform the tool's function. When you load a file into the tool — by dragging, clicking, or pasting — the browser's FileReader API reads the file's bytes into memory within the browser's process. The JavaScript then operates on that in-memory representation to produce the result. The result is rendered in the browser and, where applicable, packaged into a downloadable Blob object that you can save locally.
At no point in this workflow does any file content travel across a network connection. The tool logic, the file bytes, the processing computation, and the output all reside within your browser's sandboxed tab environment on your local device.
WebAssembly for Heavy Lifting
Several tools — particularly those involving PDF manipulation, image processing, and video operations — use WebAssembly (WASM) modules to perform computationally intensive tasks. WASM allows near-native execution speed within the browser. Modules such as PDF.js, pdf-lib, and FFmpeg.wasm are loaded once and then operate entirely locally. These modules are retrieved from a CDN on first use and cached by your browser thereafter. The modules themselves do not receive or transmit your file data.
No Account Required
ReportMedic does not require you to create an account, log in, or provide any personal information to use the tools. There is no authentication layer because there is no server-side processing to authenticate against. You open a tool, you use it, you download the result. That is the complete workflow.
Optional Human Consulting
The Fix My Report page offers access to human consulting assistance for cases where automated tools are insufficient. This is an opt-in channel. If you choose to share report details or files through this channel, you are making a voluntary submission — a deliberate choice to send information to a human consultant. This is governed separately by the Privacy Policy and Terms of Service.
Quickstart
New to ReportMedic? Here is the fastest path from landing on the site to solving your first report problem.
-
Identify your problem type
Browse the Toolbox on the home page. Tools are organised by category. If you have a mismatch between two spreadsheets, look under Comparison. If a PDF is not exporting cleanly, look under PDF Tools. If column names are inconsistent across files, look under Data Cleaning.
-
Open the tool
Click any tool card to open its dedicated page. Each tool page contains a drop zone or file picker, the tool's controls, and a results area. Read the brief description at the top of the tool to confirm it matches your use case.
-
Load your file
Drag your file onto the drop zone, click to browse and select it, or (for text-based tools) paste content directly. Most tools accept multiple common formats. Accepted formats are listed on each tool page.
-
Configure and run
Adjust any available settings — delimiter options, output format, column selections, comparison mode, etc. — then click the primary action button. Processing is typically instantaneous for files under 10 MB and completes in seconds for larger files.
-
Review and download
Results appear directly in the browser. Inspect them in the preview area, then click the download button to save the output file to your device. Nothing is saved on ReportMedic's side.
Tool Categories
ReportMedic tools are grouped into seven functional categories. Each category below includes an overview of what the tools in that group do and when to reach for them.
Data & Spreadsheet Tools
These tools operate on structured tabular data: CSV files, Excel workbooks, and similar formats. They are designed for analysts and operations teams who encounter data quality issues, schema inconsistencies, or reporting anomalies.
PDF Tools
PDF is the canonical format for distributed reports, but it is notoriously difficult to manipulate programmatically. These tools handle the most common PDF pain points without requiring Acrobat or a server-side API.
File Conversion Tools
Format conversion is one of the most repeated friction points in reporting workflows. These tools handle the most common conversion paths without loss of fidelity.
Image & Video Tools
For teams that include images, screenshots, or video clips in reports and documentation, these tools provide essential pre-publication processing.
Comparison & Diff Tools
When two versions of a file or document diverge, these tools surface exactly what changed, where, and by how much.
Text & Markup Tools
Lightweight but essential utilities for working with text, markup, and rich content in reporting and documentation workflows.
Utility Tools
General-purpose utilities for security, productivity, and common day-to-day tasks that support report and data workflows.
crypto.getRandomValues API.Full Tool Reference
The complete list of all tools is available on the Toolbox section of the Home page. Each tool card links to that tool's dedicated page, which includes inline documentation, accepted file formats, settings explanations, and example use cases. The Toolbox is the canonical, always-current index of available tools.
Tools are continuously maintained and occasionally updated. When a tool receives a significant update, a version indicator on its page reflects the change. The overall tool count currently stands at 48 tools and is growing.
Privacy Model
ReportMedic is designed from the ground up with a local-processing architecture. The following is a plain-language summary of how your data is and is not handled. For the legally operative version, refer to the full Privacy Policy.
What stays on your device
In ordinary use, all of the following remain on your device and are never transmitted to ReportMedic or any third-party server: the bytes of your loaded files, any text you paste into a tool, all processing intermediate results, and all generated output files. This applies to every tool in the Toolbox.
What leaves your device
Standard web analytics (page views, session counts, referral sources) are collected by embedded analytics scripts — these do not carry file content. The chat widget (Tawk.to) embedded on the site allows you to initiate a support conversation; anything you type into that widget is transmitted to Tawk.to's servers by design. The Link Shortener tool calls an external API to create the redirect; the URL you submit is sent to that API. These are the only data flows that cross the device boundary in ordinary use, and none of them involve your report file contents.
Sensitive data recommendations
Because processing is local, you can safely load internal financial reports, HR data exports, PII-containing spreadsheets, and legally privileged documents into the tools without concern that the file contents will be intercepted in transit or stored on a remote server — because they are never sent to one.
Browser Support
ReportMedic tools rely on modern browser APIs. The following browsers are fully supported:
- Google Chrome — version 100 and above (recommended)
- Microsoft Edge — version 100 and above (Chromium-based)
- Mozilla Firefox — version 100 and above
- Apple Safari — version 16 and above
- Opera — version 86 and above
Tools that use WebAssembly (PDF processing, video tools, OCR) require that WebAssembly is enabled in your browser, which it is by default in all modern browsers. If you are using a browser extension that blocks WebAssembly (some strict content security policy extensions do this), those specific tools may not function.
Mobile browsers are supported for most tools. However, the video processing tools (which run FFmpeg.wasm) require significant RAM — processing large video files on a mobile device is not recommended and may fail on low-memory devices. All PDF and data tools work normally on mobile.
Internet Explorer is not supported and will not be made to work — the required APIs are fundamentally absent in that browser.
File Size & Limits
Because processing is local, the practical file size limit is determined by your device's available memory and CPU speed, not by a server quota. The following are general guidelines:
- CSV and spreadsheet files: Tools handle files up to approximately 200 MB reliably on typical hardware. Files above 500 MB may cause browser tab slowness or out-of-memory conditions on machines with less than 8 GB of RAM.
- PDF files: PDFs up to 300 pages and 100 MB process reliably. Very large PDFs with embedded high-resolution images may take 30–60 seconds to process on slower hardware.
- Images: Individual images up to 50 MB process instantly. Batch operations on many images benefit from processing them in groups of 10–20.
- Video files: FFmpeg.wasm can handle video files up to several gigabytes, but processing time scales linearly with file size. A 1 GB video may take 3–10 minutes to process depending on the operation and hardware.
Shift+Esc) can help you monitor tab memory usage.
Troubleshooting
A tool is not loading or shows a blank screen
This typically indicates a JavaScript error, often caused by a browser extension (ad blocker, script blocker, privacy extension) interfering with the tool's script. Try disabling extensions for the ReportMedic domain, or open the tool in an incognito/private window where extensions are typically disabled.
My file is not being accepted
Each tool lists its accepted file formats in the drop zone area or tool description. Verify that your file's extension matches one of the listed formats. Some tools that accept CSV files may reject an XLS file even if it contains tabular data — convert to CSV first using the Excel tools or your spreadsheet application's Save As function.
The output file is empty or corrupted
This can happen if the input file is itself corrupted, password-protected (and no password was provided), or in a format that the tool does not fully support. Try opening the original file in another application to confirm it is readable, then retry. For PDF issues specifically, try the Fix Export Formatting Errors tool on the PDF first.
Processing takes a very long time
Long processing times are expected for large video files (FFmpeg.wasm), large PDF batches, or OCR on high-resolution images. A progress indicator is shown when the tool supports progress reporting. If a tool appears to have stalled (no progress for more than 5 minutes on a reasonably sized file), refresh the page and try again. Ensure no other RAM-intensive applications are competing for memory.
Converted text output has encoding errors
If extracted text shows garbled characters (e.g., ’ instead of '), the input file has a non-UTF-8 encoding. Use the Clean Dirty Data tool's encoding normalisation option, or pre-process the file in a text editor that supports encoding conversion (such as VS Code or Notepad++) and save it as UTF-8 before loading into the tool.
The PDF redaction tool shows text through the blackout
This should not occur with the ReportMedic redaction tool, which burns redactions into the rendered page content rather than simply placing an opaque overlay (which can be removed in some PDF editors). If you observe this behaviour, please contact support — it may indicate a tool issue that needs investigation.
Live Agent Help
The Fix My Report page connects you with a human consultant for report problems that are too complex, too urgent, or too domain-specific for the automated tools to address alone. This service is appropriate when:
- You have a report mismatch with financial or regulatory consequences and need a second set of expert eyes.
- The automated tools have identified a problem but you are unsure how to fix it in your specific data environment.
- You need a custom data cleaning or reconciliation script written for your exact schema and requirements.
- You are working with a report format that the tools do not natively support and need ad-hoc processing.
- You need a fast turnaround with a guaranteed SLA that automated tools cannot provide.
When submitting through Fix My Report, describe the problem clearly, the format of the data involved, and the outcome you need. Attaching anonymised or redacted sample data (not the live sensitive version) speeds up diagnosis significantly. The chat widget in the lower corner of every page is also available for immediate questions.
FAQ
Do I need to install anything?
No. All tools run entirely in your web browser. There is no desktop application, no browser extension, and no plugin to install. Open the tool page and start using it immediately.
Is ReportMedic free?
Yes. All tools in the Toolbox are free to use. The Live Agent consulting service on the Fix My Report page may involve fees depending on the scope of work — these are discussed during the consultation inquiry.
Can I use ReportMedic tools for commercial or professional work?
Yes. There are no restrictions on using the tools for professional, commercial, or enterprise purposes. Refer to the Terms of Service for the full licence conditions.
Will my files be stored or used for AI training?
No. As described in the Privacy Model section, file contents are processed locally and never transmitted to ReportMedic servers. There is no mechanism by which file contents could be used for training because they are never received by any ReportMedic system.
What if a tool doesn't support my file format?
Check the tool's accepted formats list. If your format is not supported, consider an intermediate conversion: for example, converting an ODS spreadsheet to CSV or XLSX before loading it into a data tool. If a format you need is not supported and conversion is not practical, use the chat widget to describe your use case — format support is expanded based on user feedback.
Can I run these tools offline?
Not natively — the tool pages must be served over HTTP/HTTPS. However, if you are deploying the open source version on your own infrastructure (e.g. a local GitHub Pages equivalent or a local web server), you can serve the pages from localhost and use them without an internet connection after initial WebAssembly module caching. See the Quickstart for self-hosting guidance.
Is the source code available?
The site is hosted on GitHub Pages. The repository is publicly accessible via the GitHub account associated with the site. You can inspect all tool code, report issues, and propose improvements through standard GitHub workflows.
How do I report a bug or request a feature?
Use the chat widget (bottom corner of any page) or reach out via Telegram: @ReportMedic. For bugs, include the tool name, browser version, operating system, approximate file size and type, and a description of the unexpected behaviour. Screenshots are always helpful.
Are there any rate limits or usage quotas?
No. Because processing is entirely local, there is no server resource being consumed by your usage. You can run as many files through as many tools as often as you like, without limits, without throttling, and without a usage cap.
Legal Documents
The following legal documents govern your use of ReportMedic:
- Privacy Policy — details the local-processing architecture, what information is and is not collected, and how voluntary submissions are handled.
- Terms of Service — the licence conditions, acceptable use policy, disclaimer of warranties, and limitation of liability.
- Contact — how to reach the team for support, consulting inquiries, or legal correspondence.
Documentation last updated: 2026. If something is unclear or missing, use the chat widget to let us know.