The 200 KB ceiling comes up most often on job portals, HR systems, recruitment email attachments, and profile photo uploads where the system needs a compact, recognizable image without the file overhead of a full camera photo. A typical smartphone image starts at 2 to 8 MB — anywhere from 10 to 40 times over the limit — but 200 KB is a generous budget compared to the stricter 100 KB or 20 KB rules on government exam portals. Most photos reach 200 KB through quality reduction alone, with no pixel-dimension change required.
This page presets the slider to 200 KB, so you drop in your image and press Compress. The engine runs a binary search over JPEG quality settings, encoding the actual output bytes at each step until it finds the highest quality that stays at or under 200 KB. You see the exact before-and-after sizes and the pixel dimensions before downloading.
At 200 KB, results for portraits and headshots are typically excellent. A 12-megapixel phone photo at full 4032x3024 resolution can often reach 200 KB at JPEG quality 78 to 85, where compression artifacts are invisible at normal screen viewing sizes. If your source image is unusually complex — dense foliage, heavy fabric textures, or a high-detail cityscape — the optional dimension-reduction toggle lets you shrink the long edge to bring quality back into the comfortable range.
Nothing you process here is sent anywhere. The image is decoded and re-encoded entirely in your browser, with no upload, no server, and no account required. EXIF metadata, including GPS location and device information, is stripped automatically as a side effect of the re-encode step. The tool is free and unlimited, and the same experience works on mobile and desktop.
Why 200 KB is a different kind of limit
The 200 KB ceiling behaves differently from the 100 KB or 20 KB rules you encounter on government exam portals. At 200 KB you have roughly twice the byte budget, which means most phone portraits can stay at their original pixel dimensions and reach the target through quality reduction alone — no resizing step required. A 12-megapixel iPhone photo compressed to JPEG quality 78 to 85 typically lands between 160 and 210 KB at full 4032x3024 resolution, which means the compression trade-off is barely perceptible at screen size.
That headroom is why 200 KB appears so often on job application portals, LinkedIn-style profile uploads, recruitment databases, and HR management systems. Those systems care more about database row size than image perfection; they want a photo small enough to fit in an indexed column but large enough to be unambiguously recognizable at 400 pixels wide during a review. The 200 KB number sits comfortably in that range.
Email attachments are a second common source of the limit. Many corporate email systems impose a per-attachment cap that is often 200 KB or 500 KB per image when photos are sent inline. A recruiter asking you to 'send a recent photo with your application' almost always means something under that soft threshold, even when the email does not explicitly mention a size limit. Sending a 4 MB phone photo through a corporate mail server is the fastest way to get the email flagged or silently dropped by the mail gateway.
JPEG quality settings and the 200 KB target: what to expect
JPEG compression works by dividing an image into 8x8-pixel blocks, applying a Discrete Cosine Transform to each block, and quantizing the resulting frequency coefficients. The quality parameter controls how aggressively those coefficients are rounded: at quality 95 almost nothing is discarded, and the file stays large; at quality 70 a significant fraction of high-frequency detail — fine texture, subtle shadow gradients — is rounded to zero, and the byte count drops sharply.
For a 200 KB target the quality you need depends primarily on two things: the pixel dimensions of the source and how much fine-grained texture it contains. A studio headshot on a plain background at 2000x2000 pixels usually hits 200 KB at quality 82 to 88 because the large areas of flat tone compress very efficiently. An outdoor candid with heavy foliage, complex fabric patterns, or bokeh-heavy backgrounds at the same dimensions may need quality 72 to 78 because every square centimeter has fine detail the encoder must preserve.
The binary-search approach this tool uses — encode, measure exact byte count, raise or lower quality, repeat — finds the highest quality that stays within the target rather than asking you to guess the right number. It runs five to eight encode passes in the background, each taking roughly 50 to 200 milliseconds in a modern browser, and lands within one quality point of the ceiling. The result panel shows the exact JPEG quality level chosen so you know precisely what trade-off was made.
One practical rule: if the binary search chooses quality below 65, consider enabling the dimension-reduction toggle. Dropping the long edge from 4032 to 2400 pixels reduces pixel count by 65 percent, and at 2400 pixels the image still prints at 8x6 inches at 300 DPI — more than enough for any online portal. That dimension reduction brings quality back into the 78 to 85 range, where block artifacts are invisible and the photo is still fully usable for a standard-definition screen or a printed profile.
Format guide: when JPEG, WebP, and PNG differ at 200 KB
JPEG remains the format of choice for a 200 KB photo targeting job portals, HR systems, and online forms. The reason is not technical superiority — WebP achieves 25 to 35 percent better compression at matched visual quality — but universal acceptance. Every browser, operating system, email client, and document management system from 1998 onward opens a JPEG. Some HR systems still run on Internet Explorer-based internal portals from the mid-2000s; uploading a WebP to those systems produces a broken preview or a silent rejection.
WebP becomes worth considering if your target accepts it explicitly (for example, a modern portfolio site or a web-based CV builder) and you want to stretch the 200 KB budget further. A WebP at quality 75 typically matches a JPEG at quality 85 in perceived sharpness while weighing 25 to 30 percent less. That difference means you can keep the long edge at 3000 pixels instead of 2000 pixels inside the same byte budget. If the portal you are targeting documents WebP acceptance, converting before uploading is a straightforward quality win.
PNG is the wrong format for a 200 KB photo target in nearly every case. PNG compresses losslessly, which makes it excellent for screenshots, diagrams, and flat-color illustrations, but it cannot approach 200 KB for a photographic subject at usable dimensions. A 2000x2000 PNG of a portrait typically weighs 2 to 5 MB, and there is no quality dial to turn — you can only shrink the canvas, which often defeats the purpose. The only scenario where PNG at 200 KB makes sense is a small graphic with large flat-color regions, such as a company logo or an icon, where JPEG would add ringing halos around the edges. For every other use case involving a photo, start with JPEG.
Job portals and recruitment forms: the 200 KB requirement in practice
LinkedIn stores profile photos at several resolutions internally but recommends uploads between 400x400 and 7680x4320 pixels with a 8 MB cap. Most third-party applicant tracking systems that pull LinkedIn data resample to 200 to 400 pixels for display — so any quality above the point where the photo is clear at 400 pixels is wasted bytes. A 200 KB JPEG at 1200x1200 pixels represents a sensible middle ground: it passes through every ATS import filter, displays cleanly at all review sizes, and leaves bandwidth headroom for systems still on slow server connections.
Naukri, India's largest job portal, caps profile photos at 2 MB and passport-size photos on CVs at significantly less. Many Indian corporate HR portals that integrate with Naukri's API still pass the photo through a secondary resize step that chokes on files over 200 KB, producing a blurry thumbnail or a broken image placeholder. Keeping your photo under 200 KB at the point of upload prevents the secondary resize from running at all.
Shine, Monster India, and similar portals have historically recommended photos under 200 KB in their upload dialogs, even when the hard technical limit is higher. The recommendation exists because photos stored in their database are sometimes extracted later for printed candidate dossiers, and a 200 KB JPEG reproduces acceptably on a 200-DPI laser printer at the 4x5 centimeter size typical for candidate sheets. Anything smaller risks visible block artifacts in print; anything larger wastes paper bandwidth across thousands of simultaneous PDF exports.
International job portals including Glassdoor, Indeed's CV builder, and Workday-hosted application portals generally accept photos up to 5 MB but recommend under 500 KB for upload speed on mobile connections. If you are applying from a region with 4G data constraints, a 200 KB photo uploads in under half a second on a 3 Mbps connection — fast enough that the page does not visibly pause.
Email attachments: sizing photos for reliable delivery
Corporate email gateways apply attachment filters at two levels: the per-attachment limit and the total message size limit. Both are set by the receiving mail server, not by your email client, and they vary by organization. A rough industry norm: per-attachment limits cluster at 5 MB, 10 MB, or 25 MB for general business email; but marketing-safe image embed limits for inline images in HTML email templates are often 200 KB per image, because marketing analytics platforms like Mailchimp and Campaign Monitor optimize for rendering speed.
When a recruiter or HR coordinator says 'send me your photo', they mean it will go into a template or dossier. Keeping the photo under 200 KB ensures it rounds-trips through Gmail, Outlook 365, and legacy Lotus Notes installations without triggering the gateway's inline-image stripper. A 200 KB JPEG embedded in a PDF cover letter also keeps the whole document under 1 MB for most formatted CVs, which is the informal threshold where recruiters stop downloading attachments on a phone.
For email newsletters and HTML campaigns, the 200 KB image limit is nearly a hard rule enforced by Mailchimp, Klaviyo, and similar platforms through automatic compression on upload. Sending an image at exactly or just under 200 KB means it will arrive in the inbox at close to the quality you tested — the platform may run one additional pass but it starts from a well-compressed source rather than hammering a 3 MB original down in a single step. Single-step heavy compression produces significantly more block artifacts than a two-pass approach starting from a clean 200 KB source.
Pixel dimension recommendations by use case
The right pixel dimensions depend on where the image will appear, not just the file size target. The table below gives practical starting points for the most common 200 KB use cases.
Job portal profile photo: 600x600 to 1200x1200 pixels. At 600x600 a clean 200 KB JPEG holds JPEG quality above 80 easily. At 1200x1200 you need quality 70 to 78 depending on content, which is still comfortably artifact-free for a headshot. Avoid going below 400x400 pixels — most portals enforce a minimum, and sub-400 photos display as blurry thumbnails at profile review scale.
CV or resume embedded photo: 300x400 to 600x800 pixels. Document templates typically render the photo at 3 to 4 centimeters wide. At 300 DPI print resolution that maps to roughly 350x467 pixels. A 200 KB JPEG at those dimensions holds quality above 85, producing a clean print result with no visible compression at 300 DPI. Larger pixels are wasted on the page but not harmful if file size allows.
Email attachment (standalone send): 1200x900 to 2400x1800 pixels. At these dimensions a 200 KB JPEG runs quality 72 to 80, which is clear at all screen sizes. The recipient can see detail at 1:1 zoom, which matters if they are reviewing a work portfolio or a product photo.
Email newsletter inline image: 600 to 800 pixels wide (variable height). Mailchimp and most newsletter builders display images at 600-pixel content width. At 600 pixels wide a 200 KB JPEG holds quality above 82 for most photographic content. Taller images with complex detail — infographics, product lifestyle shots — may benefit from quality 75 to 78 to keep the file size where the platform does not recompress it.
Form identity photo (government or institutional): follow the portal's exact dimension specification first. When no dimension is specified, use 600x800 pixels at quality 80 and verify the output is within 5 percent of the 200 KB ceiling. Identity photos compressed too far show block artifacts in facial features at 200-percent zoom, which can cause rejections from manual review steps.
Reading JPEG block artifacts before they cause rejections
Block artifacts are the 8x8-pixel grid pattern that appears in heavily compressed JPEGs. They show up first in areas of gradual tonal change — the soft shadow across a cheek, the smooth fade of a background gradient, the space between letters in a scanned document. At quality 75 they are visible at 200-percent zoom but invisible at 100 percent. At quality 60 they appear clearly at screen zoom. At quality 50 they degrade the overall impression even at thumbnail scale.
Two tests you can run before submitting: zoom the image to 200 percent in any image viewer and look at the face or the most critical region. If you see faint grid lines or patches of flat color where gradients should be, the quality is too low for a manual human review. The second test is to export the file, view it at the size it will be displayed on the destination form — usually 200 to 400 pixels — and check whether the detail level looks reasonable for identification. If the face is recognizable and the background does not look like a mosaic, the compression is acceptable.
A common misconception is that JPEG artifacts are visible at full resolution and therefore unacceptable. In practice, the portals and recruiters looking at your photo view it at 300 to 500 pixels on a screen — a size where JPEG quality 75 is indistinguishable from quality 95 to the human eye. The rejection risk from visible artifacts comes from two scenarios: printing the photo on a high-DPI machine, where the pixel grid enlarges to visible scale, and manual document verification where a reviewer zooms in on specific text or features. For a profile photo or standard form submission, quality 70 is the practical floor, and quality 78 to 85 is the target range where file size and appearance balance optimally at 200 KB.
How 200 KB compares to 100 KB, 500 KB, and 1 MB across real platforms
Different file-size limits exist for different institutional reasons, and knowing which limit a platform uses tells you a lot about its technical infrastructure. The table below maps four common limits to their typical contexts and the JPEG quality and pixel range that comfortably meets each one.
The 100 KB limit appears almost exclusively on government exam portals — UPSC, SSC, state public service commissions — and on university admission forms. These systems were often built on Oracle Forms or legacy PHP stacks in the early 2000s and store photos in BLOB columns sized for dial-up transfer speeds. At 100 KB you typically need to reduce pixel dimensions to 600x800 or smaller to keep quality above 70; shooting for 200 KB at those dimensions gives you room to spare and a noticeably sharper result.
The 200 KB limit dominates HR management systems, corporate ATS platforms (Taleo, SAP SuccessFactors, Zoho Recruit), and recruitment email workflows. These systems are newer but still favor compact row storage. A 200 KB JPEG at 1200x1200 pixels at quality 78 to 85 satisfies every system in this category and still reproduces cleanly at 200 DPI in a printed candidate dossier.
The 500 KB limit shows up on modern portfolio platforms, freelance marketplaces like Upwork and Toptal, and institutional faculty or staff directory pages. At 500 KB you can keep the long edge above 2000 pixels at quality 85 to 90, which is sharp enough for a professional headshot even at 150 DPI print output. This limit is generous enough that quality reduction alone — no dimension change — handles virtually every phone camera photo.
The 1 MB limit is the informal threshold for general web uploads: LinkedIn native uploads, modern government citizen portals, and e-commerce product photos. At 1 MB a standard 12-megapixel JPEG can stay at full resolution at quality 88 to 92 — the top end of the perceptually lossless range. Files above 1 MB are still fine for archives but will be auto-resampled by most display pipelines, so uploading above this threshold buys nothing visible.
| Limit | Typical platforms | Recommended pixels | JPEG quality range |
|---|---|---|---|
| 100 KB | Govt exam portals (UPSC, SSC), university admissions | 400x500 – 600x800 | 72 – 80 |
| 200 KB | HR systems (Taleo, SAP SF, Zoho), ATS, recruitment email | 800x800 – 1200x1200 | 78 – 85 |
| 500 KB | Portfolio sites, Upwork/Toptal, staff directories | 1600x1200 – 2400x1800 | 83 – 90 |
| 1 MB | LinkedIn, modern govt portals, e-commerce product | 2400x1800 – 4032x3024 | 88 – 92 |
Batch processing and workflow: handling multiple photos efficiently
When you need to compress a set of photos — a portfolio submission, a batch of event photos, or a folder of scanned ID documents — doing them one at a time through a browser tool is still feasible if you work systematically. Open the tool in one tab and keep your source files in a named folder. Process each file in sequence, downloading immediately, and use a consistent naming pattern like `[name]_200kb.jpg` so compressed outputs are instantly distinguishable from originals. This pattern prevents accidentally re-uploading an already-compressed file through the tool a second time, which typically degrades quality without recovering much file size.
The most common failure mode in batch compression is transparent PNG source files. A PNG with a transparent background re-encoded as a JPEG replaces every transparent pixel with a solid fill — usually black, because the canvas default composite is black. If your source folder contains product cutouts, logo badges, or apparel photos with transparent backgrounds, convert them to JPEG manually in Preview or an image editor first, placing the transparency over a white background before running them through the size compressor. Submitting a photo with a black border where there should be white space causes immediate form-validation rejections from portal automated checks.
Animated GIFs and animated WebPs are a second failure mode. The browser Canvas API processes only the first frame when you load an animated file into a 2D context — the resulting output is a static image, not an animation. If you need to compress an animated file, that requires a different tool; the JPEG compressor here is designed for still photography and will silently strip the animation.
CMYK color-space images — typically photos exported from Adobe InDesign or professional print workflows — can produce incorrect colors when re-encoded through the browser Canvas API, which assumes sRGB. A CMYK photo with a warm skin tone may shift to a cooler, undersaturated appearance after the Canvas encode. If you are working with photos from a print production workflow, convert to sRGB in your image editor before running them through the browser tool. The output will then be color-accurate for screen and portal display.
After compressing a batch, spot-check the outputs against the portal's requirements using the file properties panel in your OS. macOS Finder shows pixel dimensions and file size in the Get Info pane; Windows Explorer shows them in Properties > Details. Verify that dimensions meet any minimum pixel requirement the portal specifies and that the compressed file size is at or below the stated limit — not just visually similar. Portals reject files above the byte limit silently or with a generic error message, and tracking down which file caused the failure wastes significantly more time than a thirty-second spot-check batch.
Privacy: what happens to your photo
Every compression step in this tool runs inside your browser using the HTML5 Canvas API and the browser's built-in JPEG encoder. The image is decoded from the file you drop, drawn to an off-screen canvas, and re-encoded as a JPEG byte stream — a process that requires no network connection and generates no HTTP requests. The pixel data never leaves your device.
This matters more for identity and employment photos than it does for product images. A passport photo, a PAN card scan, or a professional headshot contains identifiable biometric data. Submitting it to an online compression service that operates a server-side encode means the bytes travel across the internet in both directions and sit briefly in the server's process memory. Some services retain a compressed thumbnail or log the MIME type and size. The browser-local approach used here has none of those properties: if you disconnect from the internet after the page loads, compression still works.
Re-encoding through the canvas also strips EXIF metadata, including the GPS location where the photo was taken, the device model and serial information, and the capture timestamp. The output file contains only pixel data plus a minimal JPEG header. For photos taken on a personal device at home and submitted to employers or government systems, stripping that location data is a meaningful privacy improvement that happens automatically as a side effect of the re-encode.
Where the 200 KB number actually comes from
Government online portals are the clearest example. India's passport application portal (passportindia.gov.in) specifies a 200 KB maximum for the uploaded photo with dimensions of exactly 200x200 pixels. The state of Maharashtra's various departmental portals repeat the same figure for citizen identity submissions. The UK Visas and Immigration online application system (apply for a UK visa) requires a photo file "smaller than 10 MB" for the primary passport scan but caps the separate supporting photo upload at 200 KB — the split reflects a different storage system handling supplementary documents. When you exceed the limit, the error messages are rarely polite: India's passport portal returns "File size exceeds the permissible limit," UK Visas returns a generic HTTP 413, and most state recruitment boards show "Invalid file. Max allowed size is 200KB" as a red banner that clears the file input field entirely.
Recruitment and hiring systems account for a second large cluster. The Staff Selection Commission (SSC) in India requires uploaded photos under 50 KB for admit cards but 200 KB for the detailed application form — the difference reflects where the image ends up stored. The 200 KB copy goes into a candidate database queried by evaluators; the 50 KB version is embedded into a printable PDF. Similar logic applies to the National Testing Agency (NTA) portals for JEE, NEET, and CUET: the application photo ceiling is 200 KB because the scanned image gets persisted into an Oracle database row sized for that era's storage assumptions. Job portals like Naukri and Shine have used 200 KB as a recommended or enforced maximum since approximately 2009 and have not changed it since.
University and school submission portals repeat the pattern for different reasons. Assignment portals running Moodle or Blackboard set a 200 KB cap on inline images in submitted documents because those platforms parse uploaded documents server-side, and large embedded images slow the plagiarism-detection pipeline noticeably. A Moodle instance handling 30,000 concurrent submissions during finals week needs every embedded image to be manageable — and 200 KB is small enough that a 100-page document with a dozen figures stays under 10 MB total. Visa photo upload requirements from consular e-visa systems (India e-Visa, Canada eTA photo submission guidelines) also cite 200 KB as a common ceiling, though the stated reasons differ: consular databases store the photo alongside the application record in a field with a hard byte cap set by the database schema when the system was built, often in the mid-2000s.
Quality versus resolution: which lever to pull first
Start with quality reduction, not dimension reduction. A 4032x3024 pixel phone photo at JPEG quality 80 typically produces a file between 1.8 MB and 3.2 MB depending on content complexity. At quality 60 the same image drops to roughly 700 KB to 1.2 MB. At quality 45 it reaches 350 KB to 600 KB. Quality 35 to 40 often lands the file near 200 KB — but at that level, block artifacts become visible on faces at 200-percent zoom, and fine text in the frame becomes difficult to read. So quality alone can theoretically get a 4032x3024 image to 200 KB, but the result is marginal.
The more useful approach is a two-step process: first drop the long edge from 4032 to 2400 pixels (a 40 percent linear reduction, roughly 65 percent fewer total pixels), then apply quality reduction. At 2400x1800 pixels and quality 78, a typical portrait reaches 180 to 220 KB — right in the target range, with artifacts that are invisible at screen size and acceptable at 150 DPI print. Compare that to the quality-only path: 4032x3024 at quality 38, which hits roughly 190 KB but shows grid patterns on cheekbones and noisy halos around eyelashes when the image is printed at even A5 size. The two-step approach trades 65 percent of the pixels for the ability to keep quality 30 points higher. For any use case involving human faces, that is always the better trade.
Two concrete examples measured from real phone photos: a 4000x3000 outdoor portrait under diffuse cloud cover, compressed to 200 KB two ways. Path A: quality only, no resize — ends at quality 37, 198 KB, 4000x3000 pixels. At 100-percent zoom on a 4K monitor you see 8x8 block posterization on the sky gradient and the subject's jacket. Path B: long edge to 2400, quality 80 — ends at 2400x1800 pixels, quality 80, 194 KB. At 100-percent zoom the sky gradient is smooth, fabric texture is preserved, and facial features are sharper than Path A despite fewer total pixels. The only cost of Path B is that a print above 8x6 inches at 300 DPI would show softening — but that scenario almost never applies to a photo going into a job portal or government form. For most practical submissions, resize first, then compress quality; only skip the resize step if the source image is already under 2000 pixels on the long edge.
Batch processing and EXIF metadata: what to keep and what to strip
EXIF metadata is a block of structured data embedded in every photo taken with a modern camera or phone. It records the camera make and model, lens focal length, shutter speed, ISO, capture timestamp, and — for phone photos — the GPS coordinates of where the photo was taken. A typical phone photo carries 4 KB to 12 KB of EXIF data, which is negligible against a 200 KB target. But the question of whether to keep it is not about file size.
The privacy case for stripping it is straightforward. A photo taken at your home address and submitted to a job portal or a government form database embeds your home GPS coordinates in a file that may be retained indefinitely by the receiving system. Many government portals and HR databases have had data breaches. An EXIF GPS tag is not a biometric, but it is a locator. For ID photos and employment submissions, stripping EXIF is a sensible default. This tool strips it automatically as a side effect of the Canvas re-encode: the JPEG produced by the browser Canvas API contains pixel data and a minimal JFIF header with no EXIF block. You can verify this by running `exiftool output.jpg` on the download — the output will show no GPS fields and no device serial number.
The case for keeping EXIF is narrower but real. Professional photographers submitting work samples to a printing lab or a stock photo agency need the color profile tag (sRGB or Display P3) and sometimes the capture timestamp for licensing documentation. A 200 KB ceiling is almost never imposed on those workflows — stock agencies want originals, not compressed previews — but if you are archiving a batch of photos for your own records alongside a compressed web copy, keep two folders: one with the original EXIF-intact files, one with the compressed exports for portal use. Mixing them invites accidentally uploading an uncompressed original or a stripped archive to a workflow that expected the other. For <a href="/compress-image-to-kb">general image compression</a> outside portal submissions, the same logic applies: keep originals untouched, export compressed copies to a separate output directory with a consistent naming suffix.
Checking compressed quality: a practical pre-submission checklist
The 200 KB limit behaves very differently across subject types, and the failure mode is not random. Portrait and headshot photos with a plain or blurred background compress well at 200 KB because large regions of similar color encode efficiently — the JPEG encoder spends most of its bits on the face and throws away very little visible detail. A landscape photo with dense tree canopy, a macro shot of a fabric weave, or a screenshot of text on a patterned background compresses badly at 200 KB because every 8x8 pixel block contains complex frequency components the encoder must quantize aggressively. A 200 KB headshot at quality 80 looks clean; a 200 KB screenshot of a spreadsheet at quality 80 may show blurred cell borders and smeared numerical values that make the content unusable.
Before submitting any compressed image to a form or portal, run through four checks. First, open the file at 100-percent zoom (actual pixels, not fit-to-screen) in any image viewer and look at the area of the image that matters most — a face for identity photos, text for document screenshots, a product label for e-commerce images. Second, zoom to 200 percent and look specifically at edges and gradients: straight edges that show stairstepping or halos, and smooth gradients that show banding are signs that quality was too low. Third, look at the file size in your OS file properties panel and confirm it is at or below the portal's stated limit — not merely visually similar to the source. Fourth, if the portal specifies minimum pixel dimensions, confirm the output meets them; some portals accept oversized files silently but reject undersized dimensions with a "photo too small" error even when the file is otherwise valid.
For portrait and ID photos specifically: a 200 KB JPEG is typically acceptable when the face occupies at least 40 percent of the frame, the background is plain or slightly blurred, and the photo was taken under good light with no heavy shadow. The same 200 KB limit becomes marginal when the subject is photographed against a complex background (bookshelves, outdoor foliage, patterned wallpaper), because the encoder assigns bits to background texture that the portal's automated face-detection step ignores entirely. In that situation, crop tighter before compressing — a 1.5:1 crop centered on the face reduces the complex-background area by 50 to 70 percent and allows the encoder to spend its 200 KB budget almost entirely on the subject. See also <a href="/resize-image-to-100kb">resize image to 100KB</a> for the stricter government exam portal workflow where this pre-crop step is essentially mandatory.