Validate a web app manifest JSON against the W3C specification. Check required fields, icon sizes, start URL, scope, display mode, theme colors, and installability.

Open tool

What this collection helps with

Images, favicons, and static files are easy to leave until the end of a launch. That is when small mistakes appear: the wrong path, a missing size, an unclear alt attribute, or an icon file that never reaches the published folder. These tools keep asset work concrete.

Best for

Preparing static website assets before deployment.
Checking image markup and icon references.
Keeping file paths and output folders aligned with the final public site.

Common use cases

Create image markup with useful attributes.
Plan favicon and asset paths for static hosting.
Review files that must be copied into the published output.

Task guide

Use asset tools when you prepare image markup, favicon references, and static files for a site launch or redesign. Start by gathering all image files and icon assets in a dedicated folder that mirrors your final published structure. Generate favicon HTML tags only after you have the actual icon files in the correct sizes and formats. Create responsive image markup with multiple source candidates and appropriate alt text for accessibility. Verify every asset path before deployment, because a broken image path produces a 404 or a missing visual element that no SEO tag can fix.

Publishing checklist

Verify every image and asset file path relative to your published site root, not your project folder structure.
Confirm favicon files exist at the referenced sizes and paths before adding the HTML tags to your page.
Check that responsive image srcset candidates are ordered correctly, with the smallest image first.
Validate alt text on every image for accessibility, not only on decorative elements that should use alt="".
Ensure asset files are included in your build or publish step so they reach the public folder.

FAQ

Questions about image & asset tools

Why do asset paths break after deployment?

Static builds often publish from a generated output folder. A path that works during local development may fail if the asset is not copied to the same public location. Always use paths relative to the published site root, not your source folder.

Do I need all icon sizes for a simple website?

No. A minimal favicon setup needs only a 32x32 favicon.ico and a 180x180 apple-touch-icon for iOS bookmarks. The other sizes in the generated tag list are optional and benefit larger directories or link aggregators that display rich icons.

Should I use absolute or relative URLs for image src attributes?

Use absolute URLs when images are served from a CDN or when the page may appear at multiple URL paths. Use relative URLs for local assets on a site with a stable folder structure to avoid broken paths during domain migration.

Do I need both WebP and JPEG versions of every image?

Provide a WebP source for browsers that support it and a JPEG or PNG fallback for compatibility. The responsive image markup generator creates both options when you supply the filenames, but skipping WebP is acceptable for small personal sites with minimal traffic.

What happens if I use apple-touch-icon without the actual icon file?

iOS Safari looks for apple-touch-icon references in the head and requests the file when a user bookmarks the page. If the file does not exist, the request returns a 404, and iOS shows a generic icon instead of your custom one.