Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteUse an image up to 1200 × 900 pixels for a WordPress child-theme screenshot. WordPress treats 1200 × 900 as the maximum for a theme-directory screenshot, not a mandatory exact size. A 1200 × 900 PNG is the documented reference size, but smaller dimensions are valid if the image clearly previews your child theme.
The exact WordPress child-theme screenshot requirement
The WordPress Theme Handbook says a theme-directory screenshot “must not be bigger than 1200 x 900px.” That wording establishes an upper limit: neither dimension should exceed the documented 1200-by-900 boundary. It does not establish a required minimum or say that every child theme must use exactly those dimensions. See Required Theme Files.
The handbook’s block-theme structure example labels screenshot.png as a 1200 × 900 screenshot. Treat that as a useful reference canvas, while the Theme Directory rule remains the acceptance limit. The example is documented in Theme Structure.
| Question | Practical answer |
|---|---|
| Largest permitted size | 1200 × 900 pixels |
| Required exact size? | No; the rule is a maximum |
| Recommended working canvas | 1200 × 900 pixels, then export an optimized copy |
| Minimum dimension or file weight | Not stated in the cited WordPress documentation |
| Special child-theme ratio? | None is specified |
Where the file goes—and why a child theme needs its own
Save the preview image in the child theme’s own stylesheet directory, normally the folder containing style.css. Use the conventional filename screenshot.png. WordPress core also recognizes GIF and JPEG screenshot extensions, as described by WP_Theme::get_screenshot().
#1 Best Overall
A child theme does not inherit the parent theme’s screenshot. If you want a preview displayed for the child theme in the Themes screen or associated theme directory listing, put a separate screenshot in the child folder. The child-theme relationship itself is explained in Child Themes.
wp-content/
└── themes/
├── parent-theme/
│ ├── style.css
│ └── screenshot.png
└── my-child-theme/
├── style.css
├── functions.php
└── screenshot.pngThe screenshot is a theme preview image, not a post image. It is separate from featured images and the Media Library’s Thumbnail, Medium, Medium Large and Large settings. Those content-image sizes are covered independently in Featured Images & Post Thumbnails and do not define the Theme Directory screenshot limit.
Choosing dimensions that look good in practice
Start with 1200 × 900 when you control the artwork
A 4:3 canvas gives you room to show the header, navigation, typography and a representative content area. Compose at 1200 × 900, keep important details away from the edges, and export a copy no larger than that boundary. If your design is naturally shorter or wider, use a smaller image rather than padding it with unrelated content; WordPress documentation does not prescribe a child-only aspect ratio.
Use a smaller image when the source is smaller
An 800 × 600 or 600 × 450 preview remains within the stated maximum. Do not upscale a blurry source merely to reach 1200 × 900. The screenshot’s job is to identify the child theme visually, not to meet a fictional minimum.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Rank #2
- Used Book in Good Condition
Show the child theme, not just the parent
Capture the actual child-theme result: its colors, templates, blocks, spacing, typography or custom components. If the child changes only one visible area, make that area legible while retaining enough of the page to establish context. Avoid a screenshot that is indistinguishable from the parent, because it gives users no visual reason to select the child theme.
How to create and install the screenshot
- Activate the child theme. In WordPress, open Appearance → Themes and activate the child theme so the page you capture reflects its templates and styles.
- Open a representative page. Choose a page that displays the child theme’s most important changes. Check desktop and mobile layouts before deciding which view communicates the design best.
- Capture the page. Use your browser’s screenshot command or another capture method. If the page extends below the fold, capture the full page and then crop deliberately; do not allow browser chrome, cookie notices or unrelated tabs into the image.
- Crop and compose. Set the document to 1200 × 900 pixels or a smaller proportionate size. Keep the theme’s distinctive UI visible, remove personal information and replace real user data with safe sample content.
- Export a web image. PNG is the conventional choice. JPEG is acceptable when photographic content compresses better; WordPress core also lists GIF. Check the final pixel dimensions after export.
- Install it in the child directory. Name the file
screenshot.png(or use a recognized GIF/JPEG extension) and copy it beside the child theme’sstyle.css. With a deployment tool, the destination is typicallywp-content/themes/my-child-theme/screenshot.png. - Verify the result. Return to Appearance → Themes, refresh, and inspect the child-theme card. If WordPress does not show the new image, confirm the filename, extension, directory and file permissions, then clear any page or object cache.
File and design checks before publishing
- Dimensions: neither width nor height exceeds 1200 × 900 pixels.
- Location: the file is in the child theme’s stylesheet directory, not the parent folder or Media Library.
- Name: use
screenshot.pngunless you intentionally use a core-recognized GIF or JPEG extension. - Accuracy: the image shows the active child theme and does not imply features supplied only by the parent or a plugin.
- Privacy: remove emails, names, order data, admin URLs and other identifying information.
- Legibility: text and distinctive controls remain readable at the size WordPress displays.
- Integrity: open the exported file in an image viewer and confirm it is not corrupt or accidentally saved as a different format.
Common problems and fixes
The parent screenshot appears instead
WordPress does not inherit a parent screenshot for a child theme. Add a separate image to the child theme’s own directory and use the conventional filename. Confirm that you uploaded the file to the active child theme, not merely to the parent.
The screenshot is missing from the Themes screen
Check that the file is beside style.css, that the filename is spelled correctly, and that the extension is supported. A case mismatch such as Screenshot.PNG can fail on case-sensitive servers. Refresh the Themes screen after deployment and clear caches if an older result persists.
The image is rejected or does not fit the directory preview
Re-export it so it is no larger than 1200 × 900 pixels. The official rule is a maximum, not a minimum, so reducing dimensions is preferable to stretching or adding empty borders. Also verify that you submitted a theme screenshot rather than a featured image intended for post content.
The preview looks blurry
Capture the page at a sufficient browser scale, then downsample once during export. Starting with a small, compressed screenshot and enlarging it will not restore detail. Keep key interface elements away from crop boundaries.
Changes are not visible after replacement
Make sure the replacement file has the same expected name and is in the deployed child-theme directory. Hard-refresh the browser, purge site or CDN caches, and check the file URL directly if your hosting control panel provides one.
Or skip the browser setup
ScreenshotNeo can capture a public page through one request, so you can generate the source image without configuring a browser. It removes cookie banners, newsletter popups and chat widgets before the shot. Bot checks, blank pages, failed loads and timeouts are not billed, and the response identifies the page verdict and billing status in headers. Its MCP server lets AI agents such as Claude or Cursor call screenshot tools directly.
For a page that demonstrates your child theme, replace the example URL with your publicly reachable page. After downloading the result, crop or resize it to no more than 1200 × 900 pixels and save it as screenshot.png in the child-theme directory.
See the ScreenshotNeo documentation for parameters and response details.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/child-theme-demo -o shot.webpPython
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://example.com/child-theme-demo"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com/child-theme-demo' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo includes full-page capture, device and viewport controls, retina scale, custom CSS and JavaScript, selector waits, hidden selectors, request blocking, cookies, headers, geolocation, image resizing, caching and PDF options. Those controls can help produce a clean, repeatable source, but the final child-theme file still needs to respect WordPress’s 1200 × 900 maximum.
The Free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 shots; every feature is included on every plan. Create a free ScreenshotNeo account.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Performance, reliability and cost considerations
For one release screenshot, manual capture is usually simplest. Automated capture becomes useful when you maintain several child themes, regenerate previews in a build pipeline or need identical viewport and waiting behavior on every release. A public URL is required for the API approach; local development pages must be deployed temporarily or exposed through an appropriate secure test URL.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Keep the downloaded original separate from the installed preview. This lets you regenerate a smaller PNG or JPEG without recapturing the page. If your page includes lazy-loaded images, use a full-page or wait-enabled capture so the preview does not show empty image slots. Avoid embedding secrets in query strings or custom headers when a public demonstration page can be made safe without them.
Bottom line on child-theme screenshot size
Make the child theme’s own screenshot.png no larger than 1200 × 900 pixels. A 1200 × 900 image is a documented reference size, not a required exact size. Store it beside the child theme’s style.css; do not expect WordPress to inherit the parent screenshot, and do not confuse this preview with Media Library or featured-image dimensions.
Frequently Asked Questions
Can I use a JPEG instead of PNG for a child-theme screenshot?
Yes. The WordPress core screenshot reference recognizes PNG, GIF and JPEG extensions; PNG remains the conventional filename and format.
Does WordPress require a 4:3 child-theme screenshot?
No separate child-theme aspect ratio is specified. The documented 1200 × 900 example is 4:3, while the Theme Directory requirement is expressed as a maximum size.
Should the screenshot be uploaded through the Media Library?
No. Put the screenshot file directly in the child theme’s stylesheet directory, beside style.css.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
