Frequently asked questions

EditMyStuff is a privacy-first collection of free, browser-based file tools for students and professionals — a PDF editor, a PDF Form Auto-Filler, a Resume Builder, an ITR-1 tax calculator, an AI Error Debugger, AI Handwritten Notes, and image tools. Everything runs in your browser, so your files never leave your device.

Yes. Every tool is free to use with no trial, no watermark, and no paywall. There's no account to create and nothing to upgrade. The AI features use your own free API key, so there's nothing to pay us for those either.

No. There's no sign-up and no login. Open any tool and start using it immediately — nothing to register, nothing to verify.

Live today: PDF Editor, Image to PDF, Merge PDF, Image Editor, Resume Builder, ITR-1 Calculator, AI Error Debugger, PDF Form Auto-Filler, and AI Handwritten Notes. Several more — a Meeting Transcript Analyzer, Legal Notice Generator, Invoice Generator and others — are in development and marked "Coming soon" on the home page.

Yes. The tools are touch-friendly and mobile-responsive — they work on iPhone, Android and tablets. A few tasks (like precise PDF editing) are more comfortable on a larger screen, but nothing requires a desktop.

Any modern browser: Chrome, Firefox, Safari and Edge, on both desktop and mobile. It needs JavaScript enabled. Some optional features — like on-device AI field review in the Form Auto-Filler — are only available in recent Chrome/Edge builds and are always optional.

We're actively building new tools — including a Meeting Transcript Analyzer, a Legal Notice Generator (India), a Salary Negotiation Coach, an Invoice Generator and more (see "Coming soon" on the home page). Follow the blog for launch announcements.

Use the feedback option in the app or email us. We read everything, and popular, well-explained requests tend to get built first — several current tools started as user suggestions.

No. Your file is opened, edited, and exported entirely in your browser, on your own device. It never travels over the network and is never stored on a server. Close the tab and everything is gone.

No. Because files never leave your device, there's nothing in them for us to sell or even see. We don't require accounts and we don't build personal profiles from your documents. Any basic usage measurement is privacy-respecting and never touches your files.

Your file stays in the browser tab only while it's open and is never uploaded. On a shared machine, finish your edit, download the result, and close the tab — that clears the document from memory. Avoid leaving the tab open and unattended.

Mostly, yes. Once a tool's page has loaded, editing and export happen locally, so it keeps working even if your connection drops. You only need a connection for the initial page load — and for AI features, which make a network call.

Only the AI-powered features: AI Handwritten Notes and the AI Error Debugger call an AI provider to generate their output. Every file-processing tool (PDF editing, form filling, image editing, the resume builder, the tax calculator) works offline after the page loads.

It depends on the tool. The PDF tools open PDFs; the Form Auto-Filler also handles Word (.docx) and OpenDocument (.odt) forms; image tools accept JPG, PNG and WebP. Exports include standard PDF, PNG images, and editable DOCX/ODT where relevant. Legacy binary .doc files need converting to .docx first.

There's no server-side limit, because there's no server — processing happens in your browser. The practical ceiling is your device's memory: everyday PDFs, forms and images are no problem, while very large files are limited by how much your browser can hold. You can process as many files as you like.

Yes — you always keep your output. Tools export standard PDFs, and depending on the tool you can also save PNG images or editable DOCX/ODT. The AI Handwritten Notes tool exports PDF, PNG, or prints directly.

Some tools (like AI Handwritten Notes) auto-save your work to your browser's local storage so a refresh won't lose it. Because it's local, a draft lives on that specific device and browser until you clear your site data — export a PDF whenever you want a permanent, portable copy.

Yes. The tools are free for personal and commercial use — generate resumes, fill forms, edit documents and images for work as much as you need. You own everything you create.

Not today. EditMyStuff is a web app that runs in any browser and works offline after loading, so there's nothing to install. A public API and embedding aren't available yet — if you'd find them useful, let us know and it helps us prioritise.

It's optional — AI features work out of the box. To use your own quota, open AI settings in any AI tool and add a key for Groq, Gemini, OpenAI or Anthropic; it's shared across tools so you only add it once. The key is kept in your browser (for the session unless you choose to remember it), sent with each AI request to our AI service only to call that provider, and never stored on our servers.

No — System Design is different from the other AI tools here. Its AI calls run through EditMyStuff's own server, which holds the API key, so there's nothing for you to paste or sign up for. It's free either way.

Not unless you choose to save it. A generated architecture lives in your browser tab and is yours to edit, undo/redo and export. Saving a design (optional, for a shareable link) requires signing in, and only you can edit what you've saved.

No — like System Design, the AI Presentation Maker runs its AI calls through EditMyStuff's own server, which holds the API key. There's nothing for you to paste or sign up for, and it's free either way.

Just the content. The AI only ever writes structured slide content — titles, bullet points, table data, chart values, diagram nodes — never raw HTML, CSS or pixel positions. The template you pick controls every visual detail, so the result stays properly designed. See the AI Presentation Maker for the full FAQ on templates, editing and export.

Yes. When you redact text, it's rendered into an image layer with the black box permanently baked in and the underlying text deleted. Copy-paste and text extraction return nothing — it can't be reversed.

No. The original page content is preserved and your edits are drawn on top, so text stays crisp. Inserted images are lightly downscaled only if they're very large, to keep the exported file a reasonable size.

A website QA audit is a pre-launch (or post-launch) check that a page is technically sound: its SEO metadata is present, headings and images are structured for accessibility, security headers are set, the viewport is configured for mobile, and internal links aren't broken. The Web QA Playground runs these checks automatically on any public URL and shows the evidence behind each finding. For a step-by-step walkthrough, see the pre-launch QA checklist.

It analyzes a public page's HTML and response headers and reports on SEO (title, meta description, canonical, Open Graph, headings, image alt, structured data), accessibility (missing alt text, unlabeled controls, heading order, document language, duplicate IDs, landmarks), resource performance (TTFB, HTML size, script/style/image counts and sizes), responsive configuration (viewport meta), security headers, and — optionally — a same-origin crawl for broken internal links. Every finding links to the exact evidence, and the 0–100 score is deterministic, not AI-generated.

Yes. It reports the page title and its length, the meta description, canonical URL, robots directives, the viewport tag, heading structure (H1/H2), images missing alt text, Open Graph and Twitter Card tags, JSON-LD structured data, and whether robots.txt and sitemap.xml are reachable. It's a technical/on-page SEO audit — it does not estimate keyword rankings or traffic.

Yes, for internal links. The optional crawler follows same-origin links from the page you test (up to a limit you choose, default 25) and flags any that return an error status, plus pages nothing links to. It's opt-in and polite — read-only, no re-visits, no aggressive crawling.

Yes. It reviews the response headers for HTTPS, HSTS, X-Content-Type-Options, clickjacking protection (X-Frame-Options or CSP frame-ancestors), Content-Security-Policy, Referrer-Policy and Permissions-Policy, and notes server version disclosure. This is a non-destructive, headers-only review — it never probes or attacks the site.

It runs safe, automated DOM checks: images without alt text, buttons and links without an accessible name, form controls without labels, skipped heading levels, a missing document language, duplicate IDs, positive tabindex and a missing main landmark. Automated checks catch common issues but cannot replace manual testing with a keyboard and a screen reader.

Not in this version. Field/lab metrics like Largest Contentful Paint and Cumulative Layout Shift require rendering the page in a real browser, which this tool does not do. Those metrics are shown honestly as "not available" rather than estimated. It does measure what a normal fetch can observe: server response time (TTFB), HTML size and resource composition.

No. It fetches and analyzes the page's HTML and headers; it does not render the page in a real browser or on real devices. So it reports responsive configuration (like the viewport meta tag) rather than screenshots at each device size, and it never claims device-verified results.

No. It fetches the public page through a server-side proxy that only reaches public hosts, forwards no cookies or credentials, and returns just the HTML and safe headers for your browser to analyze. Nothing you test is stored on our servers, and no data is sent to any AI service — there is no AI in the tool.

Website → Design System reads a public site's HTML and CSS and extracts its observed visual language — a color palette, typography, spacing, border radii, shadows and any real CSS custom properties — then detects UI patterns and possible consistency issues and lets you tweak components in a live playground. Everything is backed by real CSS evidence. See how to extract a design system from a website for the full walkthrough.

Yes. It parses colors from the page's CSS and inline styles — hex, rgb/rgba and hsl, including gradient stops and CSS variables — normalizes them, de-duplicates, and shows each with its occurrence count and where it was used. Frequently used colors are labelled "frequently used," never given an invented semantic name like "primary."

Yes. It collects font families (including families declared through CSS variables), a sorted type scale of font sizes, font weights, line-heights and letter-spacing, and previews them in the site's primary font where available.

Yes. Real CSS custom properties found in the source (for example --brand-500 or --radius-md) are preserved exactly, with their names and values, and shown separately from values that were merely observed from usage. Generated export variables use an --ems-extracted- prefix so it's always clear which names came from the site and which the tool created.

Yes. It detects patterns like buttons, cards, inputs, links and badges from multiple signals — semantic element, class-name hints and the resolved CSS/structure — not tag names alone. Similar elements are clustered into variants, and each pattern carries a confidence and an evidence level (observed, suggested, inferred or confirmed). When evidence is weak it says so rather than guessing.

Yes — conservatively. It flags near-duplicate colors, rare spacing or radius outliers next to a dominant value, near-duplicate font sizes and shadows, and patterns that use conflicting values. It only reports where there is deterministic evidence, so intentional variation isn't flagged, and it never produces a subjective "consistency score."

Yes. You can copy or download the extracted values as CSS custom properties and as deterministic JSON. The export contains only design values and source metadata — never cookies, headers or private data.

Only partially. It inspects the HTML and CSS as served — static style blocks, inline styles and linked stylesheets. Styles injected at runtime by JavaScript may not be visible, and when that limits coverage the tool says so instead of pretending the extraction is complete.

No. It extracts observed values and evidence-based patterns from the public CSS — that is not the same as a team's official, documented design system. "Extracted" does not mean "official." Use it to understand and reuse a site's visual language, and treat the output as a well-evidenced starting point, not a canonical spec.