The Google Forms header image size is 1600 × 400 pixels — a strict 4:1 aspect ratio, as documented in Extended Forms' guide to Google Forms header image size. Upload anything else and Google Forms forces a crop, which is why logos get clipped and headlines end up hugging the edge. Keep header files under 2MB, use PNG for logos and text, JPG for photos, and size question images around 300–500 px wide.
That's the whole spec. The rest of this article is about why images still go wrong even when people know the numbers — and the part almost nobody covers, which is how images inside questions behave differently from headers.
It's worth getting right. A form is usually the handoff point between an ad click and a captured lead. If the first thing a prospect sees is a fuzzy, mis-cropped banner, the experience feels improvised before the first field gets filled. Not fatal, but it's friction exactly where you can't afford any.
Why Google Forms Crops Your Header Image
Google Forms isn't redesigning your image. It's placing your file into a fixed 4:1 container and forcing the visible area to match. Jotform's explanation of the header constraint makes the same point: the fixed ratio routinely costs uploads their most important visual elements, especially on responsive displays.
Think of it as a panoramic frame. Put a square photo into it and something has to give — either the top and bottom get cut, or you shrink the image until the part that matters is too small to read. The platform doesn't know your logo is near the edge or that the product shot on the right matters more than the texture on the left. It just applies the frame.
The failure mode depends on the source file. Too tall, and Google trims it. Too busy, and the crop preserves the wrong region. Too small, and scaling makes it soft. Text near the edges, and part of the message vanishes or feels cramped. I've watched teams burn an afternoon nudging the in-form crop tool when the actual fix was a ten-minute rebuild of the source file at the right canvas — the crop tool lets you pick what survives, but it can't fix a badly proportioned image.
The most common trigger is recycling. A social banner or webinar graphic that's well-designed for its original placement fails inside a form, because it was composed for a different shape. Treat form graphics as their own asset class, the same way you'd respect Facebook event cover dimensions instead of reusing one image everywhere.
Google Forms Image Size Specs That Matter
Four rules cover nearly every header problem:
- Dimensions: build the file at 1600 × 400 px. Anything else invites a crop.
- Aspect ratio: 4:1, non-negotiable. This one constraint causes most display problems.
- File size: stay under 2MB for headers, per the technical guidance in Latenode's guide to Google Forms header images.
- Formats: JPG, PNG, and GIF are supported. PNG for logos and text, JPG for photos.
What happens when you break the rules is predictable: a 1600 × 400 upload displays clean; a taller image gets trimmed; an undersized image looks soft once stretched; and a text-heavy photo banner loses legibility to compression. Design the header for the form first — don't expect Google Forms to rescue a graphic built for another channel.
Note that file upload limits are a different feature with different numbers: form creators can allow respondent uploads from 1MB up to 10GB per file, with 10MB a sensible default for common documents — covered in this Google Forms file upload overview. Same lesson either way: the platform works best when you stay inside its boundaries instead of bending them.
Making Images Survive Compression
A header that fits is half the job. It also has to stay sharp after Google's processing, and compression is where ambitious designs quietly die: small text goes fuzzy first, then fine lines, then any detail sitting on a busy background.
Pick the format by content, not habit. PNG holds crisp edges — right for logos, text overlays, and flat graphics. JPG keeps photographic files light — right for photography and textured backgrounds. Neither is universally better; the question is what the user needs to perceive first.
Then design for resilience rather than beauty: text larger than feels necessary, critical elements off of detailed backgrounds, breathing room around the logo, contrast over decoration. A plain, legible header beats a visually ambitious one that turns to mush on export. Every time.
Before publishing, preview on desktop and then on a phone, and ask three questions: is the brand recognizable immediately, is the text readable without zooming, and does the header support the form's purpose or compete with it? One accessibility note while you're there — if the form uses images inside questions, add descriptive text where the platform allows it, and make sure the form still makes sense if someone can't parse the visual layer.
Image Sizes for Questions and Answer Choices
Most guides stop at the header, which skips the place teams actually get burned. Images inside questions behave differently, and official guidance is thin — Paperform's article on Google Forms headers notes that documentation for question-embedded images is limited, while users keep reporting pixelation and slow loading.
The mistake is treating question images as mini headers. Teams drop a full-size product shot or screenshot into a question and expect elegant scaling; what they get, especially on mobile, is a bloated, scroll-heavy form. The practical target for question and choice images is 300–500 pixels wide with a clean ratio — clarity with restraint, not page-filling.
What holds up in practice: tightly cropped visuals that make options easy to tell apart in product-selection forms; obvious image content with no tiny embedded labels in quizzes; screenshots in instructional forms only when they explain the task faster than a sentence would. If an image needs a paragraph to make sense, it's doing the wrong job.
Mobile is the real stress test. A choice image that looks fine on a laptop can crowd the answer area on a phone, and in multiple-choice layouts users need to compare options fast. The best question images support a decision — they shouldn't become the decision.
How to Resize an Image for Google Forms
If you're not a designer, fix the image before it ever touches Google Forms. Canva is the easiest route:
- Create a custom size design: 1600 wide, 400 tall.
- Upload your source image and drag it into the canvas, scaling until the important content sits in the center.
- If it won't fit cleanly, extend the design with a background color instead of forcing a bad crop.
- Export as PNG if the design has text or a logo, JPG if it's mostly photographic.
- Check the file weight; compress once if it's heavy, then upload.
Two habits save the most rework. Keep logos, taglines, and faces away from the outer edges — the middle of the banner is the only real estate you fully control. And preview the exported header in the form immediately, not after the whole form is built. Most "resizing problems" are really framing problems; once you build to the right canvas, Google Forms behaves.
When Google Forms Stops Being Worth the Workarounds
There's a point where designing around the tool costs more than switching tools. Google Forms remains fine for internal approvals, quick surveys, and operational odds and ends. It gets expensive — in time and in polish — when the form is part of a conversion path.
The signs you've hit the ceiling: your campaigns need the ad, landing page, and form to feel like one system; your forms need richer media handling than a single cropped banner; you're seriously optimizing conversion and want control over layout and mobile presentation; or sales depends on what the form feeds downstream.
The practical shortlist if you're comparing: OrbitForms for teams that want forms to do more than collect data — visual builder, AI lead qualification, analytics, and CRM integrations in one place. Typeform for conversational, presentation-forward forms. Jotform for template breadth and customization depth. Paperform when you want forms that read more like landing pages. The Google Forms alternative comparison lays out where each trade-off lands.
The real question isn't whether Google Forms can display an image — it can, inside its constraints. It's whether you want to keep designing around those constraints when the form is tied to trust, lead quality, and brand continuity.
Frequently Asked Questions
What size should a Google Forms header image be?
Build header images at 1600 × 400 pixels, which matches the required 4:1 aspect ratio. Images with other proportions get force-cropped by the platform, usually cutting content near the edges. Keep the file under 2MB so it loads quickly and compresses cleanly.
Why does Google Forms keep cropping my image?
The header area is a fixed 4:1 container, and Google Forms crops any upload that doesn't match it. The built-in crop tool only lets you choose which region survives — it can't fix the proportions. Rebuild the source image at 1600 × 400 with the important content centered, and the cropping problem disappears.
What image size works best for Google Forms questions?
Question and answer-choice images work best around 300 to 500 pixels wide with a simple aspect ratio. Larger images bloat the form on mobile and slow scrolling, especially in multiple-choice layouts where people compare options. Use tightly cropped visuals that make each option distinguishable at a glance.
Should I use PNG or JPG for a Google Forms header?
Use PNG when the header contains a logo, text, or flat graphics — it keeps edges crisp through compression. Use JPG for photographic or textured images, where it produces a lighter file with no visible quality loss. Both are supported, along with GIF.
How do I make a Google Forms header image not blurry?
Blurry headers almost always come from undersized source files that Google scales up, or from heavy compression on fine detail. Export at the full 1600 × 400 canvas from the original design file, avoid re-exporting from already-compressed copies, and keep small text off busy backgrounds. If typography still looks soft, switch the export to PNG.
If your forms are doing conversion work and the image workarounds are getting old, OrbitForms gives you a visual builder, AI lead qualification, and analytics without the fixed-crop gymnastics — start your 7-day free trial and rebuild your worst-looking form first.
