DEV Community: Umar

How to Scan a QR Code from a Screenshot or Photo

Umar — Thu, 12 Nov 2026 06:30:43 +0000

Someone sends you a QR code in a chat instead of a link, or your ticket arrives as a screenshot in your email. In each case the code is a picture, and pointing your phone camera at your own screen is a poor way to read it — the screen glares, and your phone's camera app cannot scan a picture that is already on the phone. The fix is a scanner that takes an image file: upload the screenshot and the code is decoded from the pixels. Our QR Code Scanner does exactly that, in your browser, with the image never leaving your device.

The method is short: save the picture as a file, open the scanner, choose the file, read the result. No app to install, no account, nothing uploaded — the decoding runs on a canvas in your own browser tab, using the jsQR library.

Upload the image and read the result

Save the picture first, then open the QR Code Scanner and use the 'Scan from image' file picker to choose it. The image is drawn onto a canvas in the page and jsQR searches the pixels; when it finds a code, the contents appear under 'Decoded' within moments, with a Copy button beside them. The picker accepts any image file your browser can open.

What you get back is the code's raw contents as plain text — usually a web address, sometimes Wi-Fi credentials, a contact card, or plain text. A Wi-Fi code reads as one line, for example WIFI:T:WPA;S:CafeGuest;P:coffee2026;; — T is the security type, S is the network name, P is the password. Reading it as text is the point: you can type the password in by hand, or read a link in full before visiting it. Nothing opens automatically. One code is read per image — crop a picture with several codes down to the one you want first.

When it says "No QR code found in that image"

The usual causes: a photo taken too far away, glare or shadow, a screenshot compressed by a messaging app until the edges turn to mush, a steep angle, or damaged print. The numbers show why cropping works: a code 300 pixels across in a 1,080-pixel-wide screenshot is 27.8% of the frame and usually decodes fine, but a 60-pixel code in a 4,032-pixel photo is 1.5% of the width — no decoder can read squares that small. Crop to a 400-pixel square around a 300-pixel code and it fills 75% of the frame. Retake closer and square-on, turn the flash off if it glares, and ask for the original if a forwarded copy is too compressed.

Read the full guide

How to Scan a QR Code from a Screenshot or Photo — the full guide has the camera alternative, the complete failure checklist, the safety check for links, and why the image never leaves your device.

Passport Photo Size: Pixels, Ratios and File Size Explained

Umar — Mon, 09 Nov 2026 06:33:55 +0000

The portal rejected your photo, and the message names a number: 600 by 600 pixels, or 35 by 45 millimetres, or a file no bigger than 50KB. A phone photo fails all three at once — it is thousands of pixels wide, the wrong shape, and several megabytes. Fixing it means three numbers in the right order: crop to the ratio, resize to the pixels, compress under the cap. The Image Resizer handles the middle step.

The order matters more than any single step. Resizing first and cropping second wastes work, because the crop throws away pixels you just sized. Compressing first and resizing second wastes quality, because compression discards detail the resize would have removed anyway. Crop to the ratio, resize to the exact pixels, compress to the cap — and check the portal spec first, because the numbers change between portals.

Read the spec first: pixels, millimetres and kilobytes

Every portal states its photo spec in three units. The US visa photo is 600 by 600 pixels, a square 2 by 2 inches at 300 DPI. A 35 by 45 millimetre photo at 300 DPI is 413 by 531 pixels — 35 millimetres is 1.38 inches, times 300 is 413. Common caps: 20KB for a signature, 50KB for a passport photo, 100KB or 200KB for general uploads. Your portal's own page is the authority: specs change.

The three steps

1. Crop to the ratio. A ratio is the shape of the photo, fixed before any resizing happens. A 600 by 600 photo is square (1:1); a 413 by 531 photo is portrait (7:9). Your phone photo is almost certainly landscape, 4:3, so it matches neither shape — and resizing never changes a photo's shape, it only scales it. Use the Image Cropper with exact X, Y, Width and Height values — for a square from a 4,032 by 3,024 photo, Width and Height 3,024 with X offset 504 centres it.

2. Resize to the exact pixels. In the Image Resizer, type the target into Width with Keep aspect ratio ticked: 600 on a square photo gives Height 600; 413 on a 7:9 portrait gives 531. Never untick the lock and type both numbers into a mismatched photo — that stretches the face, and a stretched passport photo is a rejected passport photo. Note: the resizer downloads a PNG, which stays large — step 3 fixes the file size.

3. Compress under the KB cap. In the Image Compressor, start at 80% quality and step down in 5% increments until the readout drops under your cap, aiming 5 to 10% under it. If the resized PNG refuses to shrink, convert it to JPEG first — JPEG is built for photographs, PNG is built for exactness.

Read the full guide

Passport Photo Size: Pixels, Ratios and File Size Explained — the full guide has the worked example, every pixel calculation shown, and the mistakes that get photos rejected. All three tools run entirely in your browser: your photo is never uploaded, stored or logged.

How to Remove Duplicate Lines from a List

Umar — Fri, 06 Nov 2026 06:26:06 +0000

A list picks up duplicates the moment more than one person touches it. You export email addresses from two places and merge them, and half the contacts appear twice. You combine keyword lists from three campaigns into one. You copy names out of a chat thread into a roster and the same people show up three times. Duplicates are not just untidy: an email list with repeats sends the same person the same message twice, a keyword list with repeats wastes every check you run against it, and a roster with repeats makes a headcount wrong. Cleaning the list by hand works for twenty lines and breaks down around two hundred, because the eye skips repeats it has already seen. The Remove Duplicate Lines tool does the job in one paste, and this guide covers the method, the three settings, and the invisible characters that stop two identical-looking lines from matching.

The method is short. Paste the list into the Remove Duplicate Lines tool’s Lines box and the cleaned version appears in the Unique lines box as you type, with a counter underneath reading something like 5 lines in → 3 lines out, so you can see at a glance how many duplicates were removed. Set the three checkboxes first if they matter to your list, then copy the result out with the Copy button and paste it back into your document, spreadsheet or mailing tool. The rest of this guide is about choosing those three settings correctly, because the defaults suit most lists but not all of them.

The three settings, and when to change them

Three checkboxes sit between the two boxes, and each one changes the result in a specific way. Case sensitive is ticked by default, so lines are compared exactly as typed. Keep blank lines is unticked, so empty lines are stripped out. Keep last occurrence is unticked, so the first copy of each repeated line is the one that survives. For a plain list of names or keywords, leave all three alone. Change them only when you know why: untick Case sensitive when capitalisation should not create phantom duplicates, tick Keep blank lines when blank lines separate sections you want to keep apart, and tick Keep last occurrence when the newest copy of a line is the one with the corrected content.

Case sensitive (ticked by default): lines are compared exactly as typed. Apple and apple are different lines and both survive.
Keep blank lines (unticked by default): blank lines are removed. Tick it and a blank line survives as a separator, but repeated blanks still collapse to one.
Keep last occurrence (unticked by default): the first copy of a repeated line survives. Tick it and the newest copy wins instead.

Worked example: five lines in, three lines out

The tool opens with a sample list already loaded, and it is worth watching what happens to it before you paste your own list. Five lines go in: apple, banana, apple, cherry, banana. Three lines come out: apple, banana, cherry. The second apple and the second banana are gone, the first copies stay exactly where they were, and nothing else changes — the surviving lines keep their original order and their original wording. That order-preserving behaviour is deliberate: order carries meaning in logs, rosters, instructions and ranked lists, so the tool never reorders anything. If you also need alphabetical order, dedupe first and sort afterwards in a spreadsheet, where the sort has less work to do and no repeats left to hide.

Try it with the sample: apple, banana, apple, cherry, banana goes in as 5 lines and comes out as apple, banana, cherry — 3 lines. Paste your own list over the sample and the counter updates as you type.

Exact or case-insensitive: when Ali and ali are the same entry

Case is the setting that catches most people out, because it decides what counts as the same line. With Case sensitive ticked — the default — Apple, apple and APPLE are three different lines and all four lines of Apple, apple, APPLE, Banana survive. Untick it and the three spellings share one identity, so only the first spelling is kept and the same four lines come back as just Apple and Banana. The surviving copy keeps the spelling of the first occurrence, which is the detail to check when the copies differ only in capitals: the tool never invents a spelling, it keeps the one it saw first.

Untick the option for email lists and keyword lists, where capitalisation should not create phantom duplicates — the same address typed as Ali@example.com in one export and ali@example.com in another is one person, and the same keyword in two cases is one keyword. Leave it ticked for anything where case carries meaning: codes, passwords and case-sensitive identifiers, where ABC123 and abc123 are genuinely different entries. If a list mixes the two — mostly names, but a few codes — normalise the case first with the Case Converter, which switches a whole list to lower, upper or title case in one pass, and then dedupe with the case setting left on.

Blank lines and the spaces you cannot see

Blank lines are removed by default, including lines that contain only spaces, which makes the tool handy for tightening up text pasted from PDFs and web pages. If you tick Keep blank lines, a blank line is allowed to survive as a separator between sections, but repeated blank lines are still treated as duplicates of each other, so a gap of three empty lines comes back as a single blank line. A list of alpha, then three blank lines, then beta returns as alpha and beta with the blanks stripped, or as alpha, one blank line, beta with the option ticked. The counter underneath counts every line you paste, blank ones included, so a list with three blank lines reads as more lines in than the cleaned result suggests.

The harder problem is the space you cannot see. The comparison is exact and nothing is trimmed, so a line with a trailing space and the same line without one look identical on screen and are treated as different lines: apple followed by a space, then apple on the next line, both survive. The same applies to a tab character or a non-breaking space copied from a web page, which is invisible in most editors. If a line refuses to dedupe when you can see it twice, look for trailing spaces first — retype the line by hand, or trim the spaces in the source and paste again. Paste the before and after versions into the Text Diff Checker if you want to see exactly which lines were dropped and which survived.

Keep first or keep last: which copy survives

The default keeps the first occurrence of each line in the position where it first appeared, which is the right choice for most lists: the earliest entry is usually the original, and its position is where the reader expects it. Tick Keep last occurrence and the newest copy wins instead, which suits data where the same entry was written again later with updated content, such as a re-registration or an edited settings line. The set of unique lines is the same either way; only which copy survives, and where it sits, changes. With case-insensitivity on, Apple, banana, apple becomes Apple, banana with the first occurrence kept, and banana, apple with the last occurrence kept — the later spelling survives and the line sits where its last copy was.

Doing it in a spreadsheet instead

Excel and Google Sheets both have a Remove Duplicates command — in Excel it sits on the Data tab, in Sheets under Data and then Data cleanup — and a spreadsheet is the better tool when the list lives inside a workbook with other columns, because deduping a column in place keeps the rows aligned with the data beside them. For a plain list of lines, though, the spreadsheet route is slower: open a workbook, paste the list, find the command, answer the prompt about headers, then copy the result back out. The online tool is one paste for a plain list, with the result updating as you type and no file to open or save. Use the spreadsheet when the list has neighbours; use the tool when the list is the whole job. Either way, dedupe before you sort, import or send — duplicates caught late cost more than duplicates caught at the paste.

Why the list never leaves your browser

An email list is customer data and a keyword list is business data, and both deserve more care than a random upload box on a stranger’s server. This tool splits the text on line breaks and compares each line against the ones already seen entirely in your browser, so nothing is uploaded, stored or logged, and a private list can be cleaned safely. That is the same on-device rule the whole site runs on — every tool here works the same way, which is why the privacy guide can make the claim for all of them at once. If a dedupe tool asks you to create an account before it will clean a list, that is a sign the list is the product, and you should paste it somewhere else. Browse the rest of the text tools for its companions: the case converter, the text diff checker and the word counter.

Try it now: paste the list into the Remove Duplicate Lines tool, check the counter, and copy the cleaned result back. Five minutes of checking beats an afternoon of untangling a mailing list that went out twice.

Frequently asked questions

How do I remove duplicate lines from a list online?

Paste the list into the Lines box of the Remove Duplicate Lines tool and the cleaned version appears in the Unique lines box as you type, with a counter showing lines in and lines out. Set the three options first if they matter: untick Case sensitive to merge lines that differ only in capitals, tick Keep last occurrence if the newest copy should win, and tick Keep blank lines if you want one blank separator preserved. Then copy the result out with the Copy button.

Does it treat Apple and apple as the same line?

Only if you untick Case sensitive. With case sensitivity on, the default, Apple, apple and APPLE are three distinct lines and all survive. With it off, they share one identity and only the first spelling is kept, so Apple, apple, APPLE and Banana comes back as just Apple and Banana. Untick the option for email lists and keyword lists, where capitalisation should not create phantom duplicates.

What happens to blank lines?

By default blank lines are removed, including lines that contain only spaces, which makes the tool handy for tightening up text pasted from PDFs and web pages. If you tick Keep blank lines, a blank line is allowed to survive as a separator between sections, but repeated blank lines are still treated as duplicates of each other, so you get one blank line rather than a run of them.

Should I keep the first or the last occurrence?

Keep the first occurrence for most lists: it preserves the earliest copy of a repeated line in the position where it first appeared. Keep the last occurrence when the same entry was written again later with updated content, such as a re-registration or an edited settings line. The set of unique lines is the same either way; only which copy survives, and where it sits, changes.

Will it sort my list alphabetically at the same time?

No. This tool only removes duplicates, and deliberately keeps the surviving lines in their original order, because order carries meaning in logs, rosters, instructions and ranked lists. If you also need alphabetical order, copy the cleaned list into a spreadsheet or text editor and sort it there; deduping first means the sort has less work to do and no repeats to hide.

How to Count Words in an Essay (When Characters Count)

Umar — Tue, 03 Nov 2026 09:13:56 +0000

Home / Blog / How to Count Words in an Essay (When Characters Count)
Published: 3 November 2026 · by QuikTools Hub

A school essay is usually set at 500 to 750 words, a college assignment at 1,000 to 2,500, and the Common App personal statement caps at 650 ’ and the fastest way to know where your draft stands is to paste it into the Word Counter and watch the number as you edit. Most limits carry a rough 10 percent tolerance either way, so a 500-word assignment is safe between about 450 and 550, but falling far short can cost marks just as surely as running far over. This guide covers the targets schools and universities actually set, what counts as a word when a tool and a teacher disagree, when a form means characters instead of words, and how to convert a count into reading or speaking time.

The method underneath is simple: the Word Counter splits your text on whitespace, so ’New York’ is two words and ’well-known’ is one, then totals characters with and without spaces, sentences and paragraphs alongside. Everything runs in your browser, which matters when the draft is an unpublished essay or a personal statement ’ nothing is uploaded anywhere. Start by pasting the draft, read the headline number, and only then decide whether the job is cutting, expanding, or nothing at all.

Word targets for school essays

At school level the numbers are modest and forgiving. A typical class essay or homework assignment asks for 500 to 750 words ’ roughly one to one-and-a-half pages of typed text ’ and most teachers enforce the limit loosely, caring more about structure and argument than the exact count. Longer school coursework sometimes specifies 1,000 to 1,500 words, while short exam answers are bounded by time rather than a stated count: a 45-minute essay question usually produces 400 to 600 words of handwritten text, and examiners judge against the question, not a counter. Where no target is given at all, 500 words is a safe working length for a developed answer: an introduction, three body paragraphs and a conclusion.

The penalty for missing the target at school is usually softer than students fear ’ a few marks at most ’ but the habit matters, because universities and application portals enforce caps mechanically. Learning to write to a target now means learning the two skills every longer piece of writing needs: planning how many words each section deserves before you start, and cutting the weakest 10 percent when the draft runs long. Paste the essay into the counter section by section and you will see immediately which paragraph is eating your budget.

College and university word targets

Higher education raises both the counts and the stakes. The Common App personal statement allows a maximum of 650 words, enforced by the submission box itself ’ there is no appeal, no 10 percent leeway, just a hard stop. Standard coursework essays run 1,500 to 2,500 words, seminar papers 2,500 to 5,000, and dissertations from 10,000 upward, with most institutions applying the familiar 10 percent tolerance above the stated figure (and rarely below it, though coming in dramatically short usually signals thin argumentation). Graduate school statements of purpose typically ask for 500 to 1,000 words, and scholarship essays cluster around 250 to 500. When a prompt says ’approximately’, treat the number as a target with the 10 percent band; when it says ’maximum’, treat it as a wall.

What counts as a word

Disagreements between counters come from edge rules, and knowing them saves arguments with a rubric. The standard rule ’ a word is a run of characters separated by whitespace ’ handles the ordinary cases: ’New York’ is two words, ’well-known’ is one, a standalone number like 2026 is one. Beyond that, conventions differ: hyphenated compounds are usually one word, contractions like ’don’t’ are one, and most university policies exclude the bibliography, footnotes and appendices from the count while including the main body and in-text citations. Word processors sometimes count text in headers, footers and text boxes that a marker would ignore, which is why the same essay can read 2,004 words in one tool and 1,996 in another.

Check whether footnotes, the bibliography and in-text citations count ’ policies differ by department.
Decide hyphenation rules up front: ’well-known’ as one word can swing a short essay by a few percent.
Use one counter consistently while editing, so every comparison you make is against the same rules.

Words are not characters, and forms confuse the two

An essay limit in words measures ideas; a limit in characters measures space. Five hundred words of ordinary English is roughly 2,500 to 3,000 characters with spaces, and that conversion is the bridge people reach for when a form asks for one unit and their draft is measured in the other. The two units behave differently when you edit: cutting filler phrases saves words fast, while trimming long words saves characters fast. This is also why the two tools on this site split the job deliberately ’ the Word Counter is built for writing (essays, articles, speeches), and the Character Counter is built for limits (forms, posts, SMS, meta descriptions).

When a form asks for characters, not words

Some limits are set in characters because the constraint is physical space: a submission box, a printed field, a database column. Online application portals are the classic case ’ a ’2,000 characters’ personal statement box is really asking for about 300 to 350 words ’ and social platforms, SMS and meta descriptions all count characters for the same reason. The trap is the with-spaces versus without-spaces question: most forms and platforms count every keystroke including spaces, while some academic character counts strip them. Always match the figure the form shows to the right count on the tool, and when in doubt, trust the form’s own number: it is the one enforcing the limit.

Reading time and speaking time

A word count converts neatly into time. Silent reading runs at about 200 words per minute, so a 1,200-word essay is a six-minute read and a 2,500-word assignment is twelve to thirteen minutes. Speaking runs slower, about 130 words per minute with pauses: a 650-word personal statement reads aloud in five minutes, and a ten-minute presentation needs roughly 1,300 words of script. The gap between the two rates is the one that catches people out ’ a document that looks short on the page can easily overrun a speaking slot ’ so check the speaking-time figure, not the reading-time one, before any presentation.

Hitting the target: cut or expand

If you are over, cut in passes. First remove whole sentences that repeat an earlier point ’ that is where the big savings live. Then tighten phrases: ’due to the fact that’ is five words doing the work of ’because’. If you are under, resist padding: add one more example, one counterargument addressed and answered, or one paragraph of evidence. Both jobs are easier against a live number, which is why the counter updates as you type ’ write freely, then edit against the count.

Cut the weakest 10 percent first; almost every draft has it, and the essay gets stronger as well as shorter.
Expand with substance ’ an example, a counterargument, evidence ’ never with filler phrases.
Re-check the count after formatting changes: pasting into a portal can split or merge paragraphs.

Try it: paste your essay into the Word Counter and read the headline number ’ then trim or expand until you land in range. If the form sets its limit in characters instead, the Character Counter shows both counts side by side.

Frequently asked questions

How many words should my college application essay be?

The Common App personal statement caps at 650 words, enforced by the submission box, and most successful essays land between 550 and 650. Supplemental prompts usually ask for 150 to 400 words. Write the draft freely first, then edit down into range ’ cutting the weakest 10 percent almost always makes an essay stronger, not just shorter.

Do titles, headings and the bibliography count toward the word limit?

Usually not the bibliography, and usually not appendices ’ but in-text citations often do, and headings sometimes do. The honest answer is that it depends on the department’s policy, so check the rubric or ask the marker. Use one counter consistently while editing, and keep excluded sections in a separate document so your number always reflects what will be marked.

The form says 2,000 characters ’ how many words is that?

About 300 to 350 words of ordinary English, since a word averages five to six characters plus a space. Treat that as an estimate: if the form enforces a character limit, check the character count directly ’ with spaces, which is what most forms measure ’ on the Character Counter.

Why does my word processor show a different count from the online counter?

Edge rules differ: hyphenated compounds, numbers, contractions and text in headers or footers can each swing the total by a few words. For a 2,000-word assignment a gap of five to ten words is normal and well inside the usual 10 percent tolerance. Pick one counter and stick with it while editing so your comparisons stay honest.

How long does it take to read or speak my essay aloud?

Divide the word count by 200 for silent reading minutes and by 130 for speaking minutes. A 1,000-word essay takes about five minutes to read and roughly seven minutes forty seconds to speak. For presentations, rehearse once with a timer: delivery pace on the day rarely matches silent rehearsal.

Compress Image to 100KB

Umar — Mon, 02 Nov 2026 16:21:58 +0000

The form is filled in, the documents are ready, and then the portal rejects your photo: "file size must not exceed 100KB". Your phone saved it at 2.4MB — roughly twenty-five times too big. The fix takes about a minute with the free Image Compressor: open it, set a quality level, and read the resulting file size until it lands under the cap.

This guide walks through the exact method — which quality to start at, how far to step down, and what to do when quality alone is not enough. Every step runs in your browser on the Image Compressor page, so the photo is never uploaded anywhere.

Why online forms reject your photo

Admission portals, job applications, exam registrations and visa systems all cap upload sizes because they store millions of files. A typical set of limits looks like this: signatures capped at 20KB (20,480 bytes), passport photos at 50KB (51,200 bytes), general uploads at 100KB (102,400 bytes), and supporting documents at 200KB (204,800 bytes). The numbers differ by portal, but the pattern is the same — the cap is always far below what a modern phone camera produces.

A phone photo at 2.4MB is 2,516,582 bytes. To fit a 100KB cap of 102,400 bytes, it must shrink to about 4% of its original size — a 24.58-fold reduction. That sounds drastic, but JPEG compression is designed for exactly this: it discards fine detail your eye barely notices, and at document-photo sizes the result still looks perfectly acceptable on screen and in print.

Note that portals measure in binary kilobytes, where 1KB is 1,024 bytes — not 1,000. A file your computer calls "100KB" might read as 102,400 bytes, and a portal checking strictly against 102,400 bytes will reject anything even slightly over. Always aim a little under the cap, not exactly at it.

Phone cameras are the reason this mismatch exists. A 12-megapixel sensor captures twelve million pixels, and even efficient JPEG encoding needs a few megabytes to store that much detail at high quality. Portals, meanwhile, were designed when a scanned document at 200KB was generous. Neither side is wrong; they simply optimise for different things — your phone for quality, the portal for storage. Compression is the bridge between them, and because JPEG was built for photographs, the bridge is a short one.

The method: start at 80% and step down

Open the compressor and choose your photo. The quality slider starts at 80% by default, which is the right starting point for almost every form: it visibly preserves quality while cutting most phone photos to a fraction of their size. Run the compression once and read the resulting file size, which the tool shows next to the download button.

If the result is still over your cap, move the slider down one or two notches — the slider moves in 5% steps, from 100% down to 10% — and run it again. Each run re-encodes from your original photo, not from the previous compressed version, so stepping down never stacks quality loss on quality loss. Repeat until the size reads under your portal's limit, then download.

Two practical notes. First, the tool accepts images up to 25MB (26,214,400 bytes), which covers any phone photo; anything larger needs resizing first. Second, do not chase the smallest possible file — stop at the first setting that gets you under the cap, because every step down trades away a little sharpness you cannot get back.

When you download the result, give the file a clear name before uploading. Some portals reject files with unusual characters or very long names — a different error from the size limit, and an easy one to confuse with it. Keep the name short, in plain Latin letters, and keep whatever extension the tool gives you.

Worked example: a 2.4MB phone photo under 100KB

Take a typical phone photo: 2,516,582 bytes (2.4MB), and a portal cap of 100KB (102,400 bytes). The walkthrough below shows the quality-step descent. The starting size and the cap are exact; the intermediate sizes are illustrative estimates, because the real numbers depend on how detailed the photo is — a plain sky compresses far better than a crowded street.

At 80% quality, a photo like this typically lands around 380KB — still well over the cap, but already an 85% reduction. Drop to 65%: roughly 150KB, closer but not there. Drop to 50%: roughly 90KB, under the 102,400-byte cap with a small safety margin. Three runs, each under ten seconds, and the file is ready to upload. If your photo is busier than average you might need 45%; if it is simpler, 65% could be enough — the size readout after each run tells you exactly where you stand.

Aim to land 5–10% under the cap rather than right at it. A result of 95KB against a 100KB limit leaves room for the portal's own byte-counting quirks.

When quality alone isn't enough: shrink it first

Some photos resist compression: screenshots, graphics with sharp edges, and very high-resolution images can stay stubbornly large even at 40% quality. When the slider stops helping, shrink the image dimensions before compressing. Halving the width and height quarters the pixel count, which usually does more for file size than any quality setting.

Use the Image Resizer to bring a 4000-pixel-wide photo down to 1200–1600 pixels wide — plenty for any online form — then run the smaller file through the compressor. You will find the quality slider suddenly effective again, often landing under the cap at 70–80% quality with visibly better results than a full-size image crushed to 30%. The image tools category keeps the resizer, compressor and related utilities together.

JPG vs PNG vs WebP at small sizes

Format matters as much as quality. The compressor keeps PNG files as PNG and converts everything else to JPEG — and that distinction decides whether your file can ever get small. PNG is lossless: it preserves every pixel perfectly, which makes it the wrong choice for shrinking photos. A photographic PNG will fight you all the way down the quality slider and may never reach 100KB.

For photos, JPEG is the right format at small sizes: its lossy compression is tuned for exactly this job, and virtually every portal accepts it. WebP produces even smaller files than JPEG at the same visual quality, but many government and exam portals still accept only JPG or PNG uploads, so check the portal's accepted formats before converting. If your source is a PNG photo, convert it to JPEG first — then compress.

If a portal accepts only PNG — rare, but it happens with older systems — the quality slider will barely move the needle, because PNG has no quality setting to lower in the same way. Your lever then is dimensions: resize the image down aggressively with the resizer first. A 1200-pixel-wide PNG photo is dramatically smaller than a 4000-pixel one, and for an on-screen form nobody can tell the difference.

Mistakes that make it worse

Re-compressing an already-compressed file over and over. Each pass throws away more detail; always work from the original photo, which is what the tool does on every run.
Saving a photographic image as PNG and expecting it to shrink. PNG is lossless — for photos it stays large no matter the quality setting.
Cropping out required content to hit the size cap. Portals reject photos missing the required head size, margins or background; shrink dimensions instead of cutting content.
Screenshotting a photo instead of using the original file. Screenshots add their own compression artefacts before you even start, giving you a worse result at every size.

Your photo never leaves your device

Compression here happens entirely in your browser: the tool draws your photo onto a canvas element and re-encodes it locally, then hands you the result as a download. Nothing is uploaded to any server at any point — there is no queue, no processing delay, and no copy of your ID photo sitting on someone else's machine. That is the same property explained in Which Online Tools Upload Your Files — and Which Never Do: if a tool never sends your file anywhere, there is nothing to leak, sell or breach.

This matters most for the exact documents forms ask for — ID photos, signatures, certificates. An upload-based compressor would hold a copy of your identity documents on its servers; an on-device one cannot, because the file never leaves the tab you opened.

Photo rejected again? Open the Image Compressor, start at 80%, and step the slider down until the size reads under your cap. Most forms are sorted in under a minute.

Frequently asked questions

What quality setting gets a 2.4MB photo under a 100KB cap?

Start at the default 80% and step down in 5% increments, checking the size readout after each run. A 2,516,582-byte photo typically lands under the exact 102,400-byte cap somewhere between 65% and 45% quality, depending on image detail.

My form says "maximum 50KB" — how small is that, exactly?

50KB is 51,200 bytes. Use the same method: start at 80% quality and step down until the result reads under 51,200 bytes. Leave a small margin rather than aiming for exactly the cap.

Why won't my PNG photo compress below 100KB?

The tool keeps PNG input as PNG, and PNG is a lossless format — it preserves every pixel, so photographic images stay large almost regardless of the quality setting. Convert the photo to JPEG first, then compress; JPEG's lossy encoding is designed for this job.

Can I just keep re-compressing the output to make it smaller?

That is the worst way to do it: every re-compression of an already-compressed file discards more detail and adds artefacts. Each run of the tool re-encodes from your original photo instead, so step the quality slider down on the original rather than compressing the output again.

Is it safe to compress an ID or passport photo in a browser tool?

With this tool, yes: compression runs on a canvas element inside your own browser tab and the file is never uploaded anywhere, so no copy of your identity document reaches any server. Avoid upload-based compressors for identity documents, where your file would sit on someone else's machine.

How Many Days Until Black Friday 2026? (Exact Countdown)

Umar — Mon, 02 Nov 2026 16:19:44 +0000

There are 25 days until Black Friday, Friday 27 November 2026, counted from Monday 2 November 2026. That is 3 weeks and 4 days, or 19 business days — and the Days Until Calculator on this site gives the live count for any date you pick.

The countdown in weeks, business days and months

Twenty-five days breaks down three ways, depending on what you are counting. In weeks it is 3 weeks and 4 days. In business days — Monday to Friday only — it is 19 weekdays, counted from 3 November up to and including Black Friday itself. That 19 includes Thanksgiving: Thursday 26 November counts as a business day because public holidays are not subtracted. In calendar months it is not yet a month: one full month from 2 November would reach 2 December, so Black Friday falls 5 days short of a complete month. Months here are calendar months, not 30-day blocks, which is why the figure does not divide neatly.

The 25 days add up in three parts. The rest of the first week contributes 6 days: 3, 4, 5, 6, 7 and 8 November. Then come two full weeks, 9 to 22 November, contributing 14 days. The final week contributes 5 days, 23 to 27 November. Six plus 14 plus 5 is 25 — the same total the calculator returns, and a useful check if you ever want to verify a countdown by hand.

Days until the dates around Black Friday

Thanksgiving comes first: Thursday 26 November 2026 is 24 days away, or 18 business days. Black Friday follows the next day. Small Business Saturday is 26 days away, on Saturday 28 November. Cyber Monday follows the weekend — Monday 30 November 2026 is 28 days away, or 20 business days, exactly 4 weeks from today. Between now and Black Friday there are 6 weekend days to get through: 3 Saturdays and 3 Sundays (7, 8, 14, 15, 21 and 22 November). Black Friday itself is a Friday, so it is not one of them.

The gap between the dates is the part people usually misjudge. Thanksgiving is only 1 day before Black Friday, so anything left for the holiday — travel, food shopping, guests arriving — lands on the same compressed stretch, with Black Friday landing the next day. Cyber Monday is 3 days after Black Friday, which leaves the whole weekend to compare prices before Cyber Monday. If you are counting for a deadline rather than a sale — a shipping cut-off, a promotion end date — the business-day figures matter more: 18 weekdays to Thanksgiving and 20 to Cyber Monday, before any public holidays you need to remove by hand.

Business days also decide what "arrives before Black Friday" really means. A parcel quoted at 5 business days needs 5 weekdays, not 5 calendar days — ordered on Monday 16 November, it lands on Monday 23 November, not Saturday 21 November, because the weekend does not count. Counting from today, 19 business days to Black Friday means 19 chances for a weekday delivery, a bank transfer, or a support reply — and the 6 weekend days in between are days when most of those do not move.

How the count works

Both dates are converted to UTC midnights before subtraction. That matters because local clock times shift with daylight saving: in spring a day can be 23 hours long and in autumn 25, and naive timestamp subtraction would occasionally report a day too many or too few. Business days count Monday to Friday only, and public holidays are not subtracted, since holidays vary by country — if your deadline spans one, remove that day by hand. All figures in this article are as of 2 November 2026; the calculator gives the live count for today.

Related guides

More date guides from this site: How Many Days Until Christmas 2026? — the next countdown after Black Friday, with Christmas Eve and New Year's Day alongside; Chronological Age Calculator: Exact Years, Months, Days — the exact calendar method behind date arithmetic; and How to Calculate a Percentage Increase (With Examples) — worked percentage examples with the mistakes to avoid.

Count down to your own date

Black Friday is the classic sale countdown, but the same arithmetic works for anything: a product launch, a sale end date, a holiday, an exam, a wedding, or a date in the past you want to measure. Enter any date and the calculator returns the days, weeks, business days and months, with the years-months-days figure for anniversaries. It runs entirely in your browser, with nothing uploaded and no sign-up.

The same tool runs backwards for dates in the past. A business opening, a first sale, or the day a site launched can all be measured the same way — in days, weeks and months since the date, with the years-months-days figure reading most naturally for long spans. Ten years, 3 months and 12 days means more to most people than a raw day count, but the raw count is there too when a milestone is counted in days.

One more use for the count: working backwards from a deadline. If orders must ship 5 business days before Black Friday, the last shipping day is 20 November — 19 business days minus 5 leaves 14 weekdays from today to ship. The calculator does not set the deadline for you, but it makes the arithmetic behind one exact.

Try it: open the Days Until Calculator, enter 27 November 2026, and check the countdown — then change the date to your own event and watch every figure update.

Frequently asked questions

How many days are there until Black Friday 2026?

Counted from Monday 2 November 2026, there are 25 days until Black Friday, Friday 27 November 2026. For the live count on any other day, use the Days Until Calculator.

How many business days are left until Black Friday?

19 weekdays, Monday to Friday, counted from 3 November 2026 up to and including 27 November 2026. Public holidays are not subtracted — if your deadline spans one, remove it by hand.

What day of the week is Black Friday 2026?

Friday 27 November 2026. Thanksgiving is Thursday 26 November, Small Business Saturday is 28 November, and Cyber Monday is Monday 30 November.

How many weekends are there until Black Friday?

6 weekend days fall between now and Black Friday: 3 Saturdays and 3 Sundays (7, 8, 14, 15, 21 and 22 November), counted from 2 November 2026. Black Friday itself is a Friday, so it is not one of them.

How do I count down to my own event?

Open the Days Until Calculator, enter any date, and it returns the days, weeks, business days and months — for future dates and past anniversaries alike.

Chronological Age Calculator: Exact Years, Months, Days

Umar — Fri, 30 Oct 2026 06:42:28 +0000

Sooner or later a form asks for it: school admissions, a clinic intake, a visa application, a research survey. "Chronological age." Most people type something like 36 and move on — but the form exists because "36" is not one thing. A person born in March and a person born in December of the same year are both 36 in round numbers, yet one is nearly a year older than the other, and the systems that ask for the exact number — paediatric growth charts, school birthday cut-offs, clinical trial windows — can tell the difference. Chronological age is simply the exact time elapsed since birth, counted in calendar units. This article explains what the term covers, the exact method for working it out, and the three mistakes that make rough calculators quietly wrong. The Age Calculator on this site does that arithmetic for any date of birth.

What 'chronological age' actually means

Chronological age is the calendar fact: how much time has passed since the date of birth. It earns its adjective because it is measured against two impostors that show up in the same rooms. Corrected age adjusts for premature birth — a baby born six weeks early is measured six weeks younger than the birth certificate says, and paediatricians use the corrected number for growth charts and milestones in the early years. Developmental or mental age, the language of psychology testing, describes what a child can typically do at a given age and compares the individual against it. Chronological age is the baseline both of the others are judged against: you cannot say a child is ahead or behind without first knowing exactly how old they are. Researchers prefer the word "chronological" for exactly this reason — it pins the number to the calendar and rules out the softer readings.

Paediatrics: growth percentiles and vaccination schedules run on exact age in weeks, months and years.
School admissions: birthday cut-offs ("must be 5 by 1 September") are day-exact, and siblings a year apart in the same class are the normal result of getting this right.
Youth sports: age categories exist to keep competition fair, and they are enforced to the day.
Psychology and education assessments: scores are compared against norms for the exact age band, not the rounded year.
Clinical trials and insurance brackets: eligibility windows are written in years and months, and "nearly 65" is not 65.

The exact method: years first, then months, then days

There is a standard convention, and every exact calculator follows it: count the complete years from the birth date to the most recent birthday, then the complete months since that birthday, then the leftover days. The order matters because months are different lengths — a "month" of age is not 30 days and not 30.44 days; it is one calendar month, whatever that month happens to contain. Counting years first, then months, then days respects that, which is why the answer comes out in three units instead of one big decimal.

The only tricky part is borrowing. When the day of the current date is smaller than the day of birth, you borrow the previous month's days, exactly the way you borrowed tens in school subtraction. Take someone born 31 January 1990, on 30 October 2026. Years: 2026 minus 1990 is 36, and the birthday has passed, so 36 full years. Months: January to October is 9, but the 30th is smaller than the 31st, so borrow September's 30 days — months drop to 8 and the days become 30 minus 31 plus 30, which is 29. The exact answer: 36 years, 8 months, 29 days — 13,421 days in total. Nothing was estimated; every unit came from the calendar.

A clean example, worked step by step

Now the same method on a birth date with no borrowing. Born 15 March 1990, as of 30 October 2026. First the years: 2026 minus 1990 is 36, and 15 March 2026 has already passed, so that is 36 complete years. Then the months: 15 March to 15 October is 7 complete months. Then the days: 15 October to 30 October is 15 days. The chronological age is 36 years, 7 months, 15 days — 13,378 days in total. No borrowing was needed because the 30th is larger than the 15th; when it is smaller, the previous month's days are borrowed instead, as shown above.

Check it yourself: these numbers come straight from this site's Age Calculator. Enter 15 March 1990 and it returns 36 years, 7 months, 15 days with about 13,378 days total — the same method, worked live in your browser.

Why the days actually matter

For most of adult life the days are trivia, but they stop being trivia at the boundaries. School enrolment cut-offs are counted in days — one day either side of the line decides which year a child starts. A child born on 2 September, where the cut-off is 1 September, starts school a full year later than a child born one day earlier, and every assessment, sports category and exam timetable from then on runs on that one-day difference. Paediatric medication dosing changes at exact ages. Passport and visa age thresholds, insurance brackets and pension eligibility all have a first day on which the new rule applies, and "about 17" is not the same legal fact as "17 years, 0 months, 1 day". Clinical trial windows are written the same way: eligible between 18 years 0 months and 65 years 11 months means the day counts.

Forms sometimes ask the question the other way round: "age on a specific date", usually for applications and registrations. That is the same years-months-days arithmetic with the end date fixed instead of today. And when the job is simpler — just the gap between any two dates — the Date Difference Calculator on this site covers it directly, in days, weeks and approximate months and years.

The three mistakes rough calculators make

Dividing total days by 365. This ignores leap years, and the drift is about one day every four years — 9 days across 36 years. A calculator that treats every year as exactly 365 days is quietly wrong in the small units, which are exactly the units that matter at a boundary.
Treating months as a fixed number of days. "8.5 months" is ambiguous — it could be 255 days or 261 depending on which months. Real ages are counted in calendar units, where February and July are allowed to be different.
The birthday off-by-one. Born 5 November 2018, as of 30 October 2026, the answer is 7 years, 11 months, 25 days — not 8. Any calculator that rounds to the nearest year, or counts the birthday month as complete before it arrives, gets this wrong, and a surprising number of them do.

There is a quick sanity check that catches most of these: add the answer back to the birth date and see whether you land on the target date. 5 November 2018 plus 7 years is 5 November 2025, plus 11 months is 5 October 2026, plus 25 days is 30 October 2026 — the date we started from. If a calculator's answer does not survive that round trip, the calculator is wrong.

Leap years and 29 February birthdays

Leap years enter the calculation twice, and both are handled by using real calendar lengths rather than averages. First, the borrowing step takes the actual length of the previous month — February contributes 28 or 29 days depending on the year, so no separate leap-year correction is needed. Second, the total-day count simply counts every day that passed, including every 29 February. There is nothing to add or subtract; the calendar already knows.

The one genuine edge case is a 29 February birthday. Take someone born 29 February 2000. On 28 February 2026, a non-leap year, the exact method gives 25 years, 11 months, 30 days — the birthday has not arrived, so the count stays below 26. On 1 March 2026 it reads exactly 26 years, 0 months, 0 days. Different registries and tools disagree about whether 28 February or 1 March "counts" as the birthday in non-leap years; this is the calendar-month convention the calculator here uses, stated so you can see the rule rather than guessing it.

Run your own numbers

The method above is the whole of it — years, then months, then days, with borrowing from real month lengths. If you want the arithmetic done for you, the Age Calculator on this site takes any date of birth and returns the years, months and days plus the approximate total-day count, computed in your browser with nothing uploaded. It sits with the rest of the Date & Time tools, alongside the Date Difference Calculator for plain gaps between two dates.

How Many Days Until Christmas 2026? (Exact Countdown)

Umar — Tue, 27 Oct 2026 16:37:10 +0000

Published: 26 October 2026 · by QuikTools Hub

There are 60 days until Christmas Day, Friday 25 December 2026, counted from Monday 26 October 2026. That is 8 weeks and 4 days, or 44 business days, or 1 month and 29 days — and the Days Until Calculator on this site gives the live count for any date you pick.

The countdown in weeks, business days and months

Sixty days breaks down three ways, depending on what you are counting. In weeks it is 8 weeks and 4 days. In business days — Monday to Friday only — it is 44 weekdays, counted from 27 October up to and including Christmas Day itself. In calendar months it is 1 month and 29 days: one full month from 26 October to 26 November, plus 29 days to 25 December. Months here are calendar months, not 30-day blocks, which is why the figure does not divide neatly.

The 60 days add up in three parts. October has 5 days left after today: 27, 28, 29, 30 and 31 October. November contributes all 30 of its days. December contributes 25, up to and including Christmas Day itself. Five plus 30 plus 25 is 60 — the same total the calculator returns, and a useful check if you ever want to verify a countdown by hand.

Days until the dates around Christmas

Christmas Eve comes first: Thursday 24 December 2026 is 59 days away, or 43 business days. New Year's Day follows a week later — Friday 1 January 2027 is 67 days away, or 49 business days, which makes it 9 weeks and 4 days. Between now and Christmas Day there are 16 weekend days to get through: 8 Saturdays and 8 Sundays. Christmas Day itself is a Friday, so it is not one of them.

The gap between the dates is the part people usually misjudge. Christmas Eve is only 1 day before Christmas Day, so anything left for the 24th has almost no slack — travel, food shopping and last deliveries all land on the same day. New Year's Day is 7 days after Christmas, which leaves a full week between the two holidays for visits, rest and preparation. If you are counting for a deadline rather than a holiday, the business-day figures matter more: 43 weekdays to Christmas Eve and 49 to New Year's Day, before any public holidays you need to remove by hand.

How the count works

Count down to your own date

Christmas is the classic countdown, but the same arithmetic works for anything: a birthday, a wedding, an exam, a product launch, or a date in the past you want to measure. Enter any date and the calculator returns the days, weeks, business days and months, with the years-months-days figure for anniversaries. It runs entirely in your browser, with nothing uploaded and no sign-up.

The same tool runs backwards for dates in the past. A wedding anniversary, a work anniversary, or the day a business opened can all be measured the same way — in days, weeks and months since the date, with the years-months-days figure reading most naturally for long spans. Ten years, 3 months and 12 days means more to most people than a raw day count, but the raw count is there too when a milestone is counted in days.

One more use for the count: working backwards from a deadline. If cards must be posted 5 business days before Christmas, the last posting day is 18 December — 44 business days minus 5 leaves 39 weekdays from today to post. The calculator does not set the deadline for you, but it makes the arithmetic behind one exact.

Try it: open the Days Until Calculator, enter 25 December 2026, and check the countdown — then change the date to your own event and watch every figure update.

Frequently asked questions

How many days are there until Christmas 2026?

Counted from Monday 26 October 2026, there are 60 days until Christmas Day, Friday 25 December 2026. For the live count on any other day, use the Days Until Calculator.

How many weekends are there until Christmas?

16 weekend days fall between now and Christmas Day: 8 Saturdays and 8 Sundays, counted from 26 October 2026 up to Christmas Day. Christmas Day itself is a Friday, so it is not one of them.

What day of the week is Christmas Day 2026?

Friday 25 December 2026. Christmas Eve is Thursday 24 December, and New Year's Day 2027 is also a Friday.

How many business days are left until Christmas?

44 weekdays, Monday to Friday, counted from 26 October 2026 up to and including 25 December 2026. Public holidays are not subtracted — if your deadline spans one, remove it by hand.

How do I count down to my own event?

Open the Days Until Calculator, enter any date, and it returns the days, weeks, business days and months — for future dates and past anniversaries alike.

Random Number Generator With No Repeats: Fair Draws, Raffles and Lottery Lines

Umar — Tue, 27 Oct 2026 16:35:33 +0000

Published: 23 October 2026 · by QuikTools Hub

Most random draws have a quiet flaw for everyday use: nothing stops the same number coming up twice. Draw six numbers between 1 and 49 one at a time and there is nothing unusual about getting 17 twice - each draw is independent, and the generator has no memory of what it picked a second ago. For a lottery line, a raffle or a list of winners, a duplicate is useless or worse. The fix is a setting called No repeats, and on the Random Number Generator it does exactly what the name says: every number in your draw is unique. This article explains what changes under the hood, then works through the three jobs people use it for most.

What "no repeats" changes

Statisticians call the two approaches sampling with replacement and sampling without replacement. A plain generator samples with replacement: the full range is available again for every pick, so repeats are allowed. Ticking No repeats switches to sampling without replacement - each number, once drawn, is removed from the pool, the way lottery balls are not put back in the machine between picks. The generator here does it literally: it draws, checks the result against the numbers already in your list, and discards any duplicate and draws again until the list is full of unique values.

How likely is a repeat if you leave the setting off? Much likelier than intuition suggests. This is the same effect behind the birthday paradox, where 23 strangers in a room are enough for a better-than-even chance that two share a birthday. The general rule is that collisions arrive around the square root of the range: drawing from 1 to 100, a repeat is already more likely than not after roughly a dozen draws. So a teacher picking students at random, or a giveaway drawing ten winners from a hundred entries, will hit a duplicate quickly - and whoever runs the draw then has to improvise a rule on the spot, which is exactly what a fair draw should avoid.

One hard limit: your range must contain at least as many numbers as your Count. A 1-49 range can supply at most 49 unique numbers. Ask for more and the generator stops with an error rather than quietly repeating one.

Running a lottery line

For a classic 6/49 game, set Min to 1 and Max to 49, set Count to 6, and tick No repeats. Generate, and you get six different numbers - a valid line, in the order drawn. Use the Copy button if you want to keep it. If your game has a separate bonus or power ball drawn from its own pool, that one is a separate draw with its own range, and it is allowed to match one of the main numbers, so generate it separately with No repeats off.

One thing worth saying plainly, because a lot of lottery content online implies otherwise: a no-repeats line is not luckier than any other line. Every set of six unique numbers from 1 to 49 has exactly the same chance of being drawn. The setting does not improve your odds; it simply produces a line that follows the rules of the game, with no number wasted by appearing twice. Treat it as a way to pick numbers without agonising over birthdays and anniversaries, not as a strategy.

Running a raffle or giveaway fairly

Fairness in a small draw is mostly procedure, and most of it happens before anyone clicks Generate. Number your entries first: if 137 people entered, they are entries 1 to 137, in a list anyone can inspect. Announce the rules before the draw - how many winners, and what happens if a drawn entry turns out to be ineligible - then draw with the Random Number Generator set to your entry range, Count set to the number of winners, and No repeats ticked, so the same entry cannot win twice. Do it on a shared screen or a livestream if the audience is remote; a draw people can watch is a draw people trust.

Publish the numbered entry list and the rules before drawing, not after.
Draw all winners in one go with No repeats on, and read them out in the order drawn.
If a drawn entry is ineligible - a duplicate signup, a staff member, someone who already won - do not quietly re-run the whole draw. Draw one replacement entry publicly, state why, and keep the rest of the original winners standing.
Post the winning numbers where entrants can see them afterwards, along with the entry list they were drawn from.

The replacement rule matters more than it looks. Re-rolling everything because one entry was invalid throws away valid winners and looks, from the outside, like drawing until you get a result you prefer. A single public replacement draw keeps the process defensible.

Classroom and team picks

The same mechanics cover most classroom and office jobs. Number the class list or team list, then draw. For a presentation order, draw as many numbers as there are presenters with No repeats on: the list you get is the running order. For splitting people into groups, draw the full list of numbers in one go and deal them out in order - first chunk to group one, next chunk to group two - which gives every group a genuinely mixed set rather than the front row plus friends.

Secret-santa style assignments need one extra idea. The generator draws numbers; the assignment is a mapping you make from those numbers. Draw one number per person, in list order, with No repeats on so nobody is assigned twice. If someone draws their own number, you need a rule decided in advance - the usual one is to swap that person with the next drawn entry, or redraw only that pairing while everyone watches. What does not work is quietly regenerating the whole thing until it looks right, for the same reason as the raffle: the process stops being checkable.

How the randomness works here

The integers on this page come from crypto.getRandomValues, the cryptographic random source built into your browser - the same source the Password Generator uses, put to a different job. That distinction matters. The ordinary Math.random function in JavaScript is built for speed and convenience, and its output is predictable enough that it should never decide anything of value. A cryptographic source is designed so its output cannot be guessed from previous output. The generator also maps those random values into your range carefully, rejecting the rare values that would skew the odds, so every number in the range is equally likely - no number is favoured because of how the arithmetic falls out.

It also all happens on your device. The ranges, entry counts and results are never uploaded, stored or placed in the page URL, which is a reasonable property for a draw whose entry list might be a class roster or a customer list.

Limits and honesty

This is a good tool for games, classrooms, social giveaways, team draws and picking a lottery line for fun. It is not a certified draw. Regulated lotteries, licensed prize promotions and anything with legal or significant financial stakes need an audited, certified random process with a paper trail - and, as the tool page itself warns, browser randomness should not be the sole source for regulated or high-stakes draws. If money or lawyers are involved, that warning is the whole answer.

Within those limits, the draw is as fair as the procedure around it. The generator lives among the Productivity Tools - set your range, set your count, tick No repeats, and publish your rules before you draw.

Which Online Tools Upload Your Files - and Which Never Do

Umar — Tue, 27 Oct 2026 16:34:11 +0000

Published: 22 October 2026 · by QuikTools Hub

Almost every free tool site works the same way: you choose a file, it uploads to a server somewhere, software on that server does the job, and you download the result. The site you are reading is built the other way round - every tool here runs in your browser, and your files never travel anywhere. Both designs can be legitimate, but they are not equally private, and the difference matters most for exactly the files people most often push through these tools: a scan of an ID card, a payslip, a signed contract, a personal photo that needs shrinking for a form. This article explains how each design works, and gives you two tests to run on any tool site - including this one - so you never have to take a privacy claim on trust.

How most online tools actually work

On a typical converter or compressor site, the round trip looks like this: your browser sends the file to the company's server; the server runs the conversion with programs like ImageMagick or FFmpeg; the converted file is stored, briefly or not so briefly; and your browser downloads it back. Storage windows vary - some services delete files within an hour or two and say so plainly, others are vaguer, and a file passing through a server can also end up in logs, backups and abuse-scanning systems along the way. None of this requires the operator to be dishonest or careless; it is simply what server-side processing means. Your document existed, complete and readable, on a computer you do not control.

There are fair reasons to build tools that way. Servers are powerful, they handle enormous files and exotic formats, and the processing software already exists there. If you are converting a two-hour video or a 400-page scanned archive, a server is probably the right tool. The trade-off only becomes a problem when the file is sensitive and the job is small - which, for everyday tools, is most of the time.

The other way: the tool runs in your browser

Modern browsers are quietly capable of the same work. JavaScript can read a file you select into the tab's memory, draw images onto a canvas and re-encode them at a lower quality, generate QR codes, hash text with the Web Crypto API, and produce a download - all without a single request carrying your data anywhere. Our Image Compressor works exactly like this: the image is drawn to a canvas on your device and re-encoded there, and the "download" is generated locally too. When a tool is built this way, there is no upload to intercept, retain or breach, because the file never leaves the machine it started on. It also works on a plane, which is a decent clue, as the next section shows.

Check for yourself: two tests

The network-tab test. Open the tool, press F12 (or right-click, Inspect) and go to the Network tab, then clear it. Now use the tool with a real file and watch what leaves your machine. A server-side tool shows a large request - usually a POST roughly the size of your file. A browser-based tool shows no such request: the file is never transmitted, though you will still see ordinary page and advertising requests.
The offline test. Load the tool page fully, then disconnect completely - airplane mode, Wi-Fi off, cable out. Now use the tool. If it still does the whole job and produces your download, the processing is happening on your device by definition; there was nowhere for the file to go.

Do not take our word for any of this. Run both tests on this site: load the Image Compressor, go offline, and compress a photo. It works, because there is no server in the loop to miss.

The honest part: free sites still run ads and analytics

Here is the part most "privacy-first" marketing leaves out, so we will not. A free site has to pay for itself somehow, and this one shows advertising; ad networks load their own scripts, and privacy-light analytics may count that a page was viewed. That is a real, if modest, flow of information about your visit - and it is completely separate from your tool input. The claim we make is narrow and specific: text you type, files you open, passwords you generate are processed in your tab and are not uploaded, stored, or placed in the page URL by these tools. You can read the detail on our privacy page, and the distinction is worth applying everywhere: "we may count page views" and "we receive your documents" are different claims, and only one of them should worry you about a payslip.

When a server tool is fine - and when to avoid one

Fine on a server: public or non-sensitive files, huge media your device would struggle with, obscure formats that genuinely need specialist server software.
Keep in the browser: ID and passport scans, payslips and bank documents, signed contracts, client or patient files under a duty of confidentiality, personal photos, and anything you would not email to a stranger.
Either way: a shared or public computer is its own risk - downloads and browser history stay on the machine after you leave, whatever the tool did.

The underlying point is simple: privacy claims are cheap, but architecture is verifiable. A tool either sends your file somewhere or it does not, and with a network tab and an airplane mode you can tell which in under a minute. Prefer tools that never ask for the upload in the first place - and check, the way you just learned to, rather than trusting. All 41 tools on this site are built that way; start from the homepage and run the offline test on any of them.

How Strong Is Your Password? Entropy in Plain English

Umar — Tue, 27 Oct 2026 16:32:10 +0000

Published: 22 October 2026 · by QuikTools Hub

Every password strength checker speaks the same language: bits of entropy. It sounds like physics, but entropy is really just a way of counting how many guesses an attacker would need. A password with 50 bits of entropy has about 2 to the power 50 possible combinations - roughly 1.1 quadrillion. Double the bits and you do not double the work; you square it. This guide explains where the bits come from, shows the numbers for real generated passwords, and explains why the boring advice - make it longer - beats every clever trick. If you want to check a password of your own as you read, our Password Strength Estimator gives an instant estimate, locally in your browser.

The only formula you need

Entropy (bits) = password length x log2(size of the character pool)

The pool is the set of characters each position is drawn from: 26 for lowercase letters only, more when you add capitals, digits and symbols. Log2 just converts the pool size into bits - a pool of 64 is exactly 6 bits per character, because 2 to the power 6 is 64. Every character you add multiplies the number of possible passwords by the pool size, which is why length is so powerful: with a pool of 73, each extra character makes the password 73 times harder to brute-force.

A concrete reference point: our Password Generator draws from a pool of 73 characters. That is a slightly unusual number, and it is deliberate - the generator leaves out look-alike characters (0 and O, 1 and l) so a password can be read aloud or typed from a screen without mistakes. Its pools are 23 lowercase, 24 uppercase, 8 digits and 18 symbols, so each character carries log2(73), about 6.19 bits. That gives:

8 characters - about 50 bits of entropy
12 characters - about 74 bits of entropy
16 characters - about 99 bits of entropy
20 characters - about 124 bits of entropy
For comparison: an 8-character password using lowercase letters only (pool of 26, about 4.7 bits each) has only about 38 bits - the bigger pool is worth roughly 4,000 times more combinations at the same length.

What those bits mean in practice

Take the worst realistic case: an attacker has stolen a password database with fast, weak hashing and can test 10 billion guesses per second on specialised hardware. Against a truly random 50-bit password they must try about 1.1 quadrillion combinations - a day or so of non-stop guessing, less on average. That is uncomfortably close, which is why 50 bits should be treated as a floor, not a target. At 74 bits the same attacker faces about 60,000 years of work. At 99 bits the answer runs to more than a hundred times the age of the universe. The jump from "a day" to "forever" is only a handful of extra characters.

Two honest caveats. First, these figures assume your password was chosen truly randomly, character by character - human-chosen passwords are far weaker than their length suggests, which the next section covers. Second, entropy only defends against guessing. It does nothing for a password that was reused and leaked in someone else's breach, or typed into a phishing page. Strength is necessary; it is not sufficient.

Why length beats complexity tricks

Most human password strategies add far less entropy than people think. Swapping a for @ and o for 0 is the first thing cracking software tries - those patterns are in every rule set. Appending the current year, a ! at the end, or a favourite team name adds almost nothing, because attackers try those shapes first. What actually works is raw length with randomness in it: a 16-character random string from the generator has about 99 bits no matter how it looks, while a 'clever' 9-character construction a human invented may test in the 20s. Strength estimators know this, which is why ours estimates from length and pool size and then penalises repeats, sequences and common words - paste a password into the Password Strength Estimator and a pattern-heavy one scores far below what its length promises.

Passphrases: the other way to buy length

If you must memorise a password rather than store it, a passphrase is the practical route. Five words chosen truly at random from a large word list (the classic Diceware list has 7,776 words, worth about 12.9 bits each) give you roughly 65 bits - comfortably past the floor - in something a human can actually remember and type, like a string of unrelated everyday words. The catch is the word "random": words you pick yourself drift toward predictable phrases, song lyrics and quotes, all of which are in cracking dictionaries. Roll dice or use a generator to choose the words, and the maths holds.

What to actually do

Generate, do not invent. Use the Password Generator at 16 characters or more for important accounts - that is about 99 bits, beyond any realistic brute-force attack.
Make every account unique. Entropy cannot save a password that leaks from one site and gets replayed on another.
Store them in a password manager so length and uniqueness cost you nothing to maintain.
Keep one strong memorised passphrase for the manager itself, built from randomly chosen words as described above.
Turn on two-factor authentication where it exists; it covers the cases - phishing and leaks - that entropy does not.

That is the whole subject, honestly: strength is counting, counting rewards length, and length is free when a machine does the remembering. Generate long, keep them unique, and the bits take care of themselves.

Wi-Fi QR Codes: The Format Explained

Umar — Tue, 27 Oct 2026 16:30:27 +0000

Published: 22 October 2026 · by QuikTools Hub

Point your phone camera at the little square on a cafe table and you are connected - no typing a password full of look-alike characters, no asking the staff to spell it. A Wi-Fi QR code feels like a trick, but there is no magic in it at all: the code simply contains one line of text written to a convention that phone makers agreed to recognise. Once you can read that line, you can check any Wi-Fi code before you print it, spot why a hand-made one fails to scan, and understand exactly what you are sharing. You can make one in about a minute with our QR Code Generator - it has a dedicated Wi-Fi mode - but first, the format itself.

The payload, field by field

Here is a complete, real example. Everything a phone needs to join the network "HomeNet" is in this single string:

WIFI:T:WPA;S:HomeNet;P:correcthorsebatterystaple;H:false;;

WIFI: - the opening label. It is how the scanner knows this QR code is Wi-Fi credentials and not a web link or plain text.
T:WPA - the authentication type. WPA covers WPA and WPA2 home networks. Older routers may use WEP; open networks with no password use the value nopass and leave the password field out entirely.
S:HomeNet - the SSID, which is simply your network name, exactly as it appears in a list of available networks, including capitals and spaces.
P:correcthorsebatterystaple - the password, stored as plain readable text. Hold that thought; the security section below explains why it matters.
H:false - whether the network is hidden (it does not broadcast its name). Almost every home and cafe network leaves this false.
The semicolons separate the fields, and the doubled semicolon at the end closes the string. Miss one out and strict scanners may refuse the code or quietly join the wrong thing.

That is the entire format. It was popularised by the ZXing barcode project, Apple added support to the iPhone camera in iOS 11, and Android followed - which is why virtually any phone from the last several years joins a network from a scan with no extra app. The same generator also has a vCard mode for contact cards, which works the same way: a small, standard block of text that phones know how to interpret.

Escaping: the fiddly part

Semicolons separate the fields, so what happens if your password itself contains a semicolon - or a comma, a quote, a colon, or a backslash? Those five characters have jobs inside the format, so each one must be escaped: written with a backslash in front of it. A password typed as p@ss;word has to appear in the payload as p@ss\;word. Get this wrong and the phone reads the password as ending early, then tries to join with the wrong credentials and fails without any useful error. This is the single most common reason hand-written Wi-Fi codes do not work, and it is why generating the code with a tool that escapes automatically - the QR Code Generator does - beats typing the string yourself.

An honest note on security

A Wi-Fi QR code is not a way of protecting your password. It is the opposite: it is your password, printed in a machine-readable font. Anyone who scans the code - or photographs it and scans the photo later - can read the actual password out of it in seconds. Treat a printed Wi-Fi code exactly like writing the password on a noticeboard, because that is what it is. For a guest network, a cafe, a holiday let or a workshop, that is usually fine and is the entire point. For your main home network, it is still reasonably safe while the code stays inside your house - but never post a photo of it publicly, and if one does escape, change the password and print a fresh code. For anything genuinely sensitive, the right answer is a separate guest network with its own password, which most modern routers offer.

Printing a code that actually scans

Size: 2 cm (about 0.8 inches) square is a workable minimum for a simple code on a table tent; go bigger - 3 to 4 cm - for a poster people scan from a step away, or when a long password makes the pattern dense.
Density: the more text in the payload, the more tiny squares the code needs. Long network names and long passwords both add density, so give dense codes more physical size.
Contrast and quiet zone: dark squares on a light background, with a clear margin of blank space around the code. Do not crop tight to the pattern, invert the colours, or print it over a photo.
Test before you commit: scan the printed copy with two different phones, at the distance and in the lighting where guests will actually use it. A code that only scans on your phone, up close, in bright light, will fail in the wild.

How to make one here

Open the QR Code Generator and choose the Wi-Fi tab (the other tabs make link/text codes and contact cards).
Type your network name exactly as it appears on your phone, and your password.
Pick the encryption your router uses - WPA/WPA2 for almost every modern network, WEP only for very old ones, or None for an open network - and tick Hidden network only if yours does not broadcast its name.
Click Generate QR code, then download the PNG (256, 512 or 1024 pixels - pick 1024 for print) and test-scan it before putting it out.

Everything happens in your browser: the network name and password you type are encoded on your own device and are never uploaded, which is rather the point when the thing you are encoding is a password. If a guest ever needs the details read back from an existing code, our QR Code Scanner decodes codes from an image or a camera, also locally. Browse the rest of the QR & Barcode Tools for barcodes and related utilities.