Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →First decide what “splash screen” means for your project. An installed progressive web app (PWA) may get its launch screen from app metadata on Android, while iOS and iPadOS use linked startup-image files. A decorative website or landing-page hero is different: generate an image asset, fit it to the layout, and check the responsive crops.
There is no universal splash-image size. The right dimensions and format depend on whether you are making a manifest icon, an Apple startup image, or ordinary page artwork—and on the device or component that will display it.
Choose the right kind of splash screen
The term is used for two different things. A PWA launch screen appears when someone opens an installed web app. A website hero image is artwork displayed at the top of a page, often behind or beside a headline and call to action. They have different asset requirements and implementation steps.
| What you mean | What to create | Where it is configured |
|---|---|---|
| Installed PWA on Android | App metadata and suitable icons; the platform generates the launch screen | Web app manifest |
| Installed PWA on iOS or iPadOS | Static startup-image files, potentially several variants | HTML link elements |
| Website or landing-page hero | Illustration, photograph, or other page artwork | The page’s image or hero component |
MDN describes manifest properties used for installed-app information, while web.dev explains the platform distinction for PWA startup screens: Web application manifest and iOS and iPadOS PWA startup images.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
Generate an Android PWA launch screen
For Android, the general workflow is not to make one full-screen splash bitmap. The browser and operating system can generate the launch screen from the manifest’s name, background_color, and icons. Link the manifest from your page, choose a background color that fits the app’s initial screen, and provide an appropriate app icon. See Google’s web app manifest guide and MDN’s manifest reference.
- Create or update the manifest. Include the app name, launch background color, and icon entries that suit your app.
- Link it from the document. Add a
<link rel="manifest" href="/manifest.webmanifest">element in the page’s HTML head, adjusting the path to your file. - Make the launch state coherent. Use a background color that does not clash with the first screen users see after launch, and make the icon recognizable at small sizes.
- Install and inspect on the target Android device and browser. The generated result depends on manifest metadata; do not assume a desktop tab preview reproduces an installed app’s launch experience.
This creates a platform-generated launch treatment rather than a custom, full-screen image. If the design specifically requires a custom startup image on Apple platforms, use the linked-image workflow below.
Generate iOS and iPadOS PWA startup images
The web.dev guidance describes a different approach on iOS and iPadOS: supply static image files and link them in the HTML with rel="apple-touch-startup-image". The image needs to suit the opening window. Device dimensions, portrait versus landscape orientation, and iPad multitasking window sizes can call for separate assets. Media conditions can select the relevant variants.
A basic link looks like this:
<link rel="apple-touch-startup-image" href="ios-startup.png">
For multiple variants, add separate link elements with appropriate media conditions. For example, web.dev shows using orientation conditions to distinguish portrait and landscape. The exact files and conditions should reflect the devices and window contexts you support; there is no one image that necessarily fits every launch context.
- Build-time generation: a generator can create PNG files and the corresponding HTML markup as part of asset preparation.
- Client-side generation: a script can derive an image based on device type and screen size, then inject a link element.
These approaches reduce repetitive asset setup; they do not remove the need to validate the output. Test the relevant device, orientation, and iPad window sizes, and verify that the correct image is selected when the app opens. Read web.dev’s iOS and iPadOS startup-image guidance for the platform workflow.
Generate a website or landing-page hero image
A hero image is ordinary page artwork, not a PWA startup asset. Generate it separately from the page’s text and controls so the headline and call to action remain editable, responsive, and accessible as HTML.
Rank #2
- Decide what the image must communicate. Name the product, service, place, or idea. Choose whether the image should be photographic, illustrative, conceptual, or a product mockup.
- Write a focused visual brief. Specify the subject and scene, visual style, composition, lighting or mood, and brand palette. State where the real headline and button will go so the image leaves clear space there. Add constraints such as no lettering, logos, watermark, or interface controls if those should not appear.
- Generate distinct directions. Compare meaningful alternatives—for example, different subject placements or visual treatments—rather than only making tiny wording changes to one prompt.
- Review the artwork in the actual page layout. Put it behind or beside the real copy, at desktop and narrow mobile widths. Check legibility, brand fit, focal-point visibility, and whether cropping removes important parts of the subject.
- Export to suit the component. Select dimensions and format based on the image’s destination, delivery pipeline, and quality or performance needs. Do not treat a suggested canvas size as a universal splash-image specification.
- Integrate and inspect the real page. Test responsive behavior and loading in the implemented hero component. Keep essential words and controls in HTML, not baked into the image.
Prompt template
Use this as a starting brief and adapt it to your image generator:
Create a [photographic / illustrated / stylized] [landing-page hero background / website visual] for [brand, product, or service]. Show [specific subject and scene]. Compose it in a [wide / other target] frame with [subject placement] and clear negative space on [left / right / top] for a real HTML headline and call to action. Use [brand colors or palette], [lighting and mood], and [visual references described in plain language]. Keep the focal subject recognizable at mobile crop sizes. No lettering, logo, watermark, UI controls, or fake text. Output as [format] at dimensions appropriate to [actual component].
Recommended Free Tools
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
If the result is close but not usable, revise one issue at a time—such as focal-point placement or empty space for copy—then check the revised image in the layout again.
Choose image dimensions and format for the destination
Do not search for one fixed “website splash screen size” and apply it everywhere. A manifest icon, an iOS startup image, and a hero background serve different purposes and are displayed in different contexts. Choose the canvas from the destination’s requirements, then test the actual result on the devices and layouts that matter.
For generated artwork, the OpenAI image API documents controls for image size and output format, including PNG, JPEG, and WebP. The supported options depend on the selected model, so use its current reference rather than copying a dimension from an unrelated example: OpenAI Create image API reference. A design tool can also provide an in-canvas workflow: Figma describes generating hero-image options within a design canvas connected to a design library, then reviewing and refining them there. See Figma’s hero image generator overview. Treat that as one workflow example, not as a substitute for checking the exported asset in your site.
Or skip the browser setup
If you need a screenshot of the finished page rather than a generated artwork file, ScreenshotNeo is a website screenshot API and MCP server for developers. One GET request can return a PNG, JPEG, WebP, or PDF. For example, using cURL:
PC 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 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchcurl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
Replace the example URL with your page and supply an API key. See the ScreenshotNeo API documentation for request options and response details. Screenshot capture is useful for reviewing how a hero sits with live page copy; it does not replace generating or configuring the underlying artwork.
- Cookie and consent banners are accepted before capture, and more than 60 known consent platforms, newsletter popups, and chat widgets are removed; each step can be turned off.
- Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed. Response headers indicate the page verdict and billing status.
- An MCP server provides
take_screenshot,get_page_info, andcapture_pdftools for AI agents and MCP clients. - The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshooting common problems
Android launch screen does not match the intended design
Check that the installed app is using the manifest you edited, that the manifest link resolves, and that its name, background color, and icons are the intended values. Then test the installed app on the target browser and device; an Android launch screen is generated from those values rather than loaded as a custom full-screen bitmap.
An iPhone or iPad shows no custom startup image
Confirm that the page includes a valid apple-touch-startup-image link and that its file path loads. If you provide variants, inspect their media conditions and verify the image fits the window context in which the PWA opens.
The image is cropped badly on mobile
The source may be composed for a wider frame than the mobile hero displays. Move the subject or reserve more space around it, and inspect the crop in the actual responsive component. If separate responsive assets are part of your implementation, select them deliberately rather than assuming one crop will work everywhere.
Rank #4
Generated image contains fake text or a logo
Keep page typography and controls in HTML, and explicitly ask the generator for no lettering, logos, watermarks, or UI controls. Regenerate or edit the art rather than relying on incorrect generated lettering in a live page.
The file is too large or looks poor after export
Choose a format and dimensions suitable for the destination and compare the exported result at its real display size. Check the current capabilities of the chosen image model or tool; supported sizes and formats differ, and a larger canvas is not automatically better for a page component.
Free tools Windows power users keep installed
One-click scans. No signup required.
Keep the workflow reliable and efficient
- Separate artwork from implementation. Generate the visual asset, then configure the manifest, link elements, or page component that displays it.
- Validate on target contexts. PWA launch screens should be checked on installed apps and relevant devices; hero images should be checked at actual desktop and mobile breakpoints.
- Keep text accessible and editable. Store the headline, button labels, and essential information as page content rather than embedding them in a background image.
- Balance image quality with delivery needs. Pick dimensions and format for the display context and loading requirements, then review the exported file in the finished experience.
- Recheck volatile tool options. Image model parameters, formats, and constraints may change; consult the current documentation for the specific generator you use.
Frequently Asked Questions
Can I use the same splash image for Android and iPhone PWAs?
Not necessarily. Android generally generates its launch screen from manifest values, while iOS and iPadOS use linked startup-image files.
Should I put the landing-page headline inside the generated image?
Usually no. Keep the headline and controls as HTML so they remain editable, responsive, and available as page content.
What should I test before publishing a hero image?
Review it in the implemented layout at desktop and narrow mobile widths, checking crop, subject visibility, copy legibility, and brand fit.
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.
