WebToLayers
WebToLayers converts websites to Photoshop documents. In other words, the app allows you to screenshot webpages by keeping each...
Description
WebToLayers converts websites to Photoshop documents. In other words, the app allows you to
screenshot
webpages by keeping each element in a separated layer. The app will save you lots of time when re-designing or improving existing web pages.
Additional features :
• Safari extension
• Custom page
size
• Custom web agent
• JS Injections
This version has been optimized for macOS High Sierra and later. Moreover, the application is available in 7 languages (English, French, German, Spanish, Italian, Japanese and Chinese). Feedback can be sent directly from the app. In this way, you can contact us for any suggestions and improvements in few clicks.
WHAT’S NEW
Version 1.4.0:
• Fixed Issues: Resolved several minor issues to enhance overall performance and functionality.
REQUIREMENTS
• Intel, 64-bit processor
• macOS 11.0 or later
ScreenShots
:
If you are using Adblocker!! Please support this website by adding us to your whitelist. Ads are what helps us bring you premium content! Or read this to know how you can support us. Thank you!
Size
– 7.3MB
Previous Versions
Editor-checked details
Recommended for web/UI designers, product managers and documentation teams that need an existing page as an annotatable, rearrangeable PSD. Workflow: confirm capture rights; remove account/payment data; fix URL, viewport, scale, user agent, language and fonts; wait for complete loading; export PSD plus PNG/JPEG; compare dimensions and key elements in the target editor; keep, rename and group useful layers; rebuild text, buttons and components from the design system instead of treating capture as production source; document canvas/iframe/animation limitations; archive with manifest and SHA-256. Use Photoshop for deep bitmap work, or compare Pixelmator Pro and Acorn for lighter Mac editing.
Pros
- It moves a whole webpage into a PSD workflow, where separated visual elements are more useful than a flat screenshot for proposals, annotation, rearrangement and rapid mock-ups. Parallel PNG/JPEG output helps detect PSD displacement. Custom page dimensions and user agent simulate desktop, tablet and phone canvases. Safari extension, cache cleaning, force reload and JavaScript injection assist repeatable capture. It is small and focused for designers reviewing an existing page or sketching a redesign. The developer specifies macOS 11+ and M1 optimisation.
Cons
- A rendered page is not a reversible design source: complex CSS, canvas, video, iframes, Shadow DOM, pseudo-elements and composited layers may be rasterised, merged or omitted, while fonts and cross-origin rules can change text. It does not create maintainable HTML/CSS or replace browser devtools, Figma components or a design system. Sessions, CAPTCHAs, consent overlays, region locks and lazy loading reduce reproducibility. Long pages increase time, memory and layer noise. JavaScript injection is a security risk. Version 1.4.0 is older and should be benchmarked on a current macOS/Safari setup before critical use.
Installation steps
- The site package is WebToLayers 1.4.0. The official requirement is macOS 11.0 or later; version 1.3.2 added M1 optimisation, while 64-bit Intel is also supported. Copy the app to Applications, then benchmark a public static page that needs no sign-in. Enter the full HTTPS URL, set page dimensions or user agent, wait for assets to load, and export PSD plus a PNG/JPEG visual reference. Open the PSD in Photoshop, Pixelmator Pro or Acorn and inspect canvas size, layer count/order, transparency, text and image placement. Test JavaScript injection only on copies and non-sensitive pages, using trusted scripts. For repeatable batches, fix viewport, scale, language, session and fonts; record URL, capture time and SHA-256.
Uninstallation steps
- Before removal, retain source PSDs, PNG/JPEG references, page URLs, viewport/user-agent settings, capture times, notes and required licence records. Create a manifest and SHA-256 for important PSDs, then reopen them in a target editor to confirm layers remain editable. Dynamic pages may not be reproducible, so preserve a PDF or browser archive when the page itself is a deliverable. Never bundle login cookies, tokens, personal data or injection scripts. Move exports into project storage, quit and remove the Safari extension through browser extension settings, then delete the app. Before clearing preferences/caches, record settings and avoid removing shared data used by other NeededApps products.
Common errors and fixes
- For blank pages or missing assets, open the same URL in Safari to verify network, TLS, regional access and page availability, then wait for lazy assets and retry. Sign-ins, CAPTCHAs, consent overlays and single-page apps may capture only current rendered state; fix window, session and scroll position. Font substitution can result from missing local fonts, web-font CORS or incomplete loading—retain a font list and compare the PNG. Canvas, video, iframe, Shadow DOM, CSS compositing and pseudo-elements may not become separate editable layers; this is a visually layered PSD, not HTML/CSS source. If export fails, reduce page height, stop animation/video, clean cache and force reload; very long pages consume memory. On M-series Macs check app build and native/Rosetta launch state. Remove failed injected scripts and never debug them on account or payment pages.
What changed in this version
- Official notes for WebToLayers 1.4.0 say that several issues were resolved to improve overall performance and functionality. The directly preceding 1.3.2 introduced a macOS 11-style icon, M1 optimisation, clean-cache and force-reload actions, plus interface fixes. Its core remains whole-page PNG/JPEG capture or PSD conversion that attempts to preserve each HTML element as a separate layer, with custom page size and user agent. This summary stops at 1.4.0 and does not mix in later rewrites.
Alternatives
Screenshots
