Ekramul Hoque

How EkZapp started

EkZapp began the way most side projects do — out of a recurring annoyance rather than a grand plan. I kept needing small, specific things done to files and numbers: compress a PDF small enough for an exam form upload, convert a cheque amount into words without making a typo, check whether a scanned photo met a government portal's exact pixel and file-size requirements. Every existing option online was either buried in ads, demanded an account and email signup for a task that should take ten seconds, or quietly watermarked the output unless I paid. None of that made sense for something this simple, so I started building my own versions, one tool at a time, alongside a full-time day job.

What began as a handful of PDF utilities for my own use gradually turned into a full platform once I noticed the same tools solving the same frustrations for other people too — the traffic and feedback made it clear this wasn't just a personal itch. I kept adding categories from there: image tools, calculators, business utilities, and now a growing set of guides on the blog that go deeper into the "why" behind a tool, not just the "how."

What I've built

EkZapp now covers 100+ tools across five main categories, each one added because a specific, recurring task needed a faster and cleaner solution than what was already out there:

Beyond the tools themselves, I write guides on the blog that go into more depth than a tool page usually allows — things like how PDF password encryption actually works, or what changed in this year's ITR filing rules — because a tool alone doesn't always answer the "why" someone landed on the page in the first place.

My approach to building tools

• No signup, ever. Every tool on EkZapp works without creating an account or handing over an email address — if a task takes ten seconds, the tool shouldn't take longer than that to access.
• Files aren't stored longer than necessary. Uploaded files are processed and then cleaned up — nothing sits around on a server after you've downloaded your result.
• Client-side where it makes sense. Calculators and converters that don't need server processing — like the amount-in-words tool — run entirely in your browser, so the numbers you type never leave your device.
• I read every piece of feedback. There's no support team behind EkZapp — if something's broken or a tool doesn't do what you expected, the message reaches me directly, and I fix what I can.
• Built for real, specific problems. New tools generally come from noticing the same frustrating, narrow requirement show up repeatedly — an exam board's exact photo size rule, a bank's cheque-writing convention — rather than copying whatever a competitor already offers.

Why finance and document tools specifically

A good chunk of what I build now sits in the calculator and document category — income tax, GST, EMI, cheque amounts in words — and that's not accidental. Indian tax and finance paperwork is full of small, precise requirements that are easy to get wrong by hand: a mismatched cheque amount, a wrongly chosen tax regime, an ITR form that doesn't match your income type. These mistakes are usually invisible until a bank rejects a cheque or a return gets flagged, at which point fixing them costs far more time than getting it right the first time would have.

I try to build these tools the way I'd want to use them myself under real deadline pressure — the Income Tax Calculator, for instance, compares both regimes side by side rather than making you guess, because "which one is cheaper for me" is the actual question people have, not "what are this year's slab rates" in the abstract.

How I keep the content accurate

Anything involving dates, tax rules, or eligibility limits on this site — ITR deadlines, Section 87A rebate thresholds, ITR form eligibility — is checked against the Income Tax Department's official notifications and other authoritative sources before it's published, and rechecked whenever a Budget or CBDT circular changes something. Rules like these shift most years, sometimes with a last-minute deadline extension, so I try to keep pages updated rather than leaving outdated figures live once something changes. If you ever spot something that looks out of date, the contact link above reaches me directly.

The tech behind EkZapp

EkZapp runs on Flask and Python, hosted on Render, with each tool built as its own route and template rather than a single monolithic app — this keeps individual tools easy to update or rebuild without risking breakage elsewhere on the site. PDF processing uses libraries like PyMuPDF and pypdf; image tools rely on Pillow for most operations, with a dedicated background-removal API for that specific task after an earlier in-house approach turned out too resource-heavy for a small hosting plan. Calculators that don't need file processing — tip, income tax, amount-in-words — run entirely as client-side JavaScript, so results appear instantly without a round trip to the server.

Running this on a single free-tier hosting plan means paying close attention to memory and processing limits that a bigger operation wouldn't have to think about — which is part of why some tools have practical size or page-count limits, and why I test changes against real, sometimes messy files rather than only clean sample documents.

Common questions people ask me

• Is EkZapp really free? Yes — every tool is free to use, with no hidden premium tier or paywalled feature. The site is supported by ads, which is also why you'll see them on tool pages.
• Do you store my files? No. Uploaded files are processed for your specific task and then cleaned up — they aren't kept, browsed, or used for anything beyond generating your download.
• Why build this alone instead of a team? It started as a personal side project solving my own problems, and staying solo has let me ship and fix things quickly without needing to coordinate across a team — the tradeoff is that some features take longer since it's just me working on this around a day job.
• How do you decide what to build next? Mostly from search patterns, direct feedback, and my own recurring frustrations with paperwork and files — if the same specific need keeps showing up, it usually becomes the next tool or guide.
• Can I request a tool? Yes — the contact link above reaches me directly, and a good number of tools on the site exist because someone asked for exactly that.

Design decisions and accessibility

Every tool page on EkZapp is a standalone HTML template rather than inheriting from a shared base layout — a deliberate choice that costs some duplication in the codebase but means one tool's page can never accidentally break because of a change made for a different tool. Design-wise, I've moved toward a more visual, example-driven layout across the site over time — comparison tables instead of paragraphs of caveats, use-case cards instead of a generic feature list — after noticing that a wall of unbroken text is exactly what makes a free tool site feel thin and unhelpful, even when the underlying tool works fine.

Accessibility matters here too: semantic HTML, reasonable color contrast, and ARIA labels where a plain tag isn't enough, since a chunk of visitors are filling out an accessibility-relevant form themselves (accessible PDFs, alt-text-ready images) and deserve a site that isn't fighting them on the way there.

What's next for EkZapp

The current focus is deepening the Text and Developer tool categories with the same level of detail already applied to the PDF, Image, Business, and Calculator sections — word counters, case converters, JSON formatters, and similar utilities that currently exist but haven't had the same content and design pass yet. Alongside that, the blog is growing into a proper resource in its own right rather than just a set of tool companion pages, covering topics like ITR filing deadlines, PDF encryption, and exam-form document requirements in more depth than a tool page alone allows.

Longer term, the plan is the same as it's always been: keep building the specific, narrow tools that solve a real recurring frustration, keep them free and signup-free, and keep this page updated as that list grows past 100.

Working alongside a full-time job

EkZapp isn't my main job — it's built and maintained during evenings and weekends, alongside a separate day job. That constraint shapes a lot of practical decisions here: why some tool updates roll out in small batches rather than all at once, why I lean on straightforward, well-tested libraries instead of building everything from scratch, and why the site's design has steadily improved over time rather than launching polished from day one. It also means response times to feedback or bug reports can take a day or two rather than being instant, though I do try to get to every message that comes through the contact page.

I mention this not as an excuse but because I think it's relevant context for anyone reading a tool page or a guide here — this is a genuinely independent, single-person project, not a funded startup with a support team behind it, and the tools reflect the priorities of someone actually using them for the same real-world tasks you probably are. If a tool ever feels like it was built by someone who's actually filled out the same form or hit the same file-size wall, that's not a coincidence — it usually means I have.