One-time downloads · $2.99–$9.99 USD. No subscription.

Perunlight

Step-by-step guide

HeimScope

Turn a list of authorised pages into a reviewed redesign scope, with screenshots, decisions and a local handoff.

You are planning a website redesign or clean-up with a client and need an agreed, numbered list of the site's pages, with a screenshot and a decision for each page.

Get HeimScope · $4.99

Read the guide and download the practice files free. The $4.99 one-time purchase supplies the prepared program and guide bundle. The program retains its included no-charge preview-use permission; it does not require an activation key.

See it in use

Capture a four-page fictional site

A screenshot walkthrough with fictional practice data. Select a step to explore.

1. Start with

Capture a four-page fictional site

A local demo shop and urls.txt define exactly four pages.

Sample files and contents

examples/heimscope-native-0.1.3/site/ contains a synthetic demo shop. urls.txt lists exactly four pages. examples/heimscope/ and examples/reports/ are retained historical 0.1.2 practice data.

Practice files and guides are free. The complete app is included only where the product page says so.

2. In the app

Actual HeimScope 0.1.3 in ordinary Chrome 152/Linux. The pass processed all four fictional pages.
The pass processed all four fictional pages. Enlarge image ↗

Try it in three steps

  1. Serve the fictional site and create a local capture project.
  2. Grant Chrome prompts and run the four-page pass.
  3. Export CSV, HTML and JSON; review pages before assigning decisions.
Show every click and setting
  1. From the extracted bundle, run python3 -m http.server 9128 --bind 127.0.0.1 --directory examples/heimscope-native-0.1.3/site.
  2. Enter http://127.0.0.1:9128 as origin, paste examples/heimscope-native-0.1.3/urls.txt, validate and create the inventory.
  3. Grant both actual Chrome prompts, run the pass and wait for four processed pages.
  4. Export CSV, HTML and JSON after the pass; review the four captured pages and assign groups and decisions before any real client handoff.
  5. Revoke both grants and stop the local server.

3. The result

Inspect the result

The draft inventory records four captured pages and images. Human groups and decisions remain unfinished.

Actual HeimScope 0.1.3 in ordinary Chrome 152/Linux. CSV, HTML and JSON are available after capture; four human decisions remain.
CSV, HTML and JSON are available after capture; four human decisions remain. Enlarge image ↗
What to check in the practice result

Four captured fictional pages, with matching URL/title pairs and four images embedded in the local HTML. Saved example outputs are drafts with no human groups or decisions.

This fictional example is shown in the working interface and in the supplied result. Review the guide before using your own files.

See the workflow at a glance

Choose a short explanation, then follow the worked example below. Check the requirements and compatibility before using your own files.

Agree the page list before the redesign quote.

Six pasted addresses do not necessarily mean six pages to redesign. In HeimScope's fictional tool-library example, one duplicate and one off-site address are excluded, leaving four pages to inspect. Export a standalone HTML inventory with screenshots and a CSV for the scope discussion. You supply the URLs: this is not an automatic crawler. The extension installs manually in desktop Chrome Developer mode. A four-page capture and export were checked on Linux; the full 50-page limit and real agency projects remain unverified.

View the illustrated card
Agree the page list before the redesign quote. — the same explanation written above, with a labelled illustrative panel.
Download the full-size PNG card

Decide with a real example

A small, local workflow for a manually reviewed redesign scope.

  1. Inspect the handoff first

    Open the free HTML report, CSV and illustrated guide. They come from four fictional pages.

    See the worked example

  2. Check installation and permissions

    Russian-only unpacked Chrome extension. Capturing needs a broad all-websites grant; revoke it afterwards.

    Read the setup steps

  3. Know what is still manual

    You provide URLs, group the pages and decide what stays. The tool does not crawl or approve the scope.

    Read the limits

Before you start

  • Desktop Chrome with Developer mode. Exact 0.1.3 Load unpacked and actual permissions/capture were tested in ordinary Chrome 152.0.7977.82 on Linux; Windows/macOS and other versions are unverified.
  • Russian-only interface. English instructions below include the exact Russian button labels.
  • One site you are authorised to inspect and its page addresses. No automatic crawling or page discovery.
  • Permission to read the chosen site and Chrome’s broad screenshot permission (<all_urls>: read and change data on all websites). Revoke access after the pass.
  • The purchased heimscope-0.1.3-guide-bundle.zip contains program/heimscope-preview-0.1.3.zip. The included preview requires no activation key.

Your first result

  1. Install the inner preview program

    Extract heimscope-0.1.3-guide-bundle.zip, then program/heimscope-preview-0.1.3.zip to a stable folder. In chrome://extensions enable Developer mode, choose Load unpacked, and select the inner extension/ folder containing manifest.json. Keep that folder in place.

  2. 1. Проект — choose one site and list its pages

    Enter the site’s scheme, host and port in Разрешенный сайт (origin), then paste the addresses into Адреса страниц, по одному в строке. Click Проверить список and inspect exclusions. Click Создать ведомость to create the numbered inventory. This is a manual URL list, limited to 50; start with the four-page example.

  3. 2. Проход — grant access and capture

    Click Разрешить доступ к … and Allow in Chrome’s actual site prompt. Then click Разрешить снимки (<all_urls>) and Allow the separate broad prompt. Старт stays unavailable until both grants exist. Click Старт and leave the capture window in front. The exact 0.1.3 build captured four fictional pages in ordinary Chrome 152/Linux.

  4. 5. Экспорт — follow the remaining-work card

    Проверить страницы opens pages missing a group or decision; Продолжить проход returns to pending captures. Exports are disabled while a pass is preparing, running or paused. Finish or cancel before exporting. Draft exports identify unfinished work; they are not client approval.

  5. 3. Ведомость — make the decisions

    For each page enter a template group and choose сохранить (keep), переделать (rework) or убрать (remove). The page leaves the remaining-review list only after both fields are complete. On a narrow screen each page becomes a vertical card. Review notes, screenshots and 4. Исключения; grouping and decisions are yours, not automatic.

  6. Save and hand off the reviewed scope

    Wait for the saved state before closing the tab. In 5. Экспорт choose CSV для сметы, HTML для клиента or Файл проекта (JSON). CSV/HTML seal that inventory version; the next edit creates a new one. HTML includes the screenshots and opens locally. Exporting or opening it does not constitute client approval. Inspect paths and site content before sharing.

  7. Revoke access and keep a backup

    Return to 2. Проход and click Отозвать разрешение на снимки. Chrome may also remove the narrower site grant; if Отозвать доступ is still enabled, revoke it too. Confirm Старт is unavailable. Export a JSON backup: uninstalling the extension deletes its local projects. Stored projects reopen in the same Chrome profile; JSON import moves them to another installation.

  8. Update an existing installation

    Export JSON from the old installation first. Extract the new inner ZIP to a stable folder and Load unpacked its extension/ folder. Import the backup and inspect pages and images; a different folder can have a different extension ID and storage. Retain the old installation until verified.

A worked example

Capture four fictional pages in ordinary Chrome 152/Linux

Input: examples/heimscope-native-0.1.3/site/ contains a synthetic demo shop. urls.txt lists exactly four pages. examples/heimscope/ and examples/reports/ are retained historical 0.1.2 practice data.

  1. From the extracted bundle, run python3 -m http.server 9128 --bind 127.0.0.1 --directory examples/heimscope-native-0.1.3/site.
  2. Enter http://127.0.0.1:9128 as origin, paste examples/heimscope-native-0.1.3/urls.txt, validate and create the inventory.
  3. Grant both actual Chrome prompts, run the pass and wait for four processed pages.
  4. Export CSV, HTML and JSON after the pass; review the four captured pages and assign groups and decisions before any real client handoff.
  5. Revoke both grants and stop the local server.

Expected result: Four captured fictional pages, with matching URL/title pairs and four images embedded in the local HTML. Saved example outputs are drafts with no human groups or decisions.

Troubleshooting

Старт is disabled.

Read the permission message. Both the chosen-site grant and the separate all-websites screenshot grant are required. If you do not want to grant them, do not run the capture.

Export buttons are disabled during a capture pass.

Finish or stop the pass first. A paused pass still owns the inventory. This protects newly arriving page results; you can export the saved draft after stopping.

The review card still lists pages.

Each page needs both a template group and a decision. Pending captures are counted separately. Select the remaining-review action, complete the fields and inspect exclusions.

The save status is pending or reports a failure.

Keep the tab open. Do not treat an edited field as durable until saving finishes. Resolve the visible storage or conflicting-tab error before export; keep a JSON backup after successful saving.

The site-access revoke button is already disabled.

Chrome can remove the narrower grant when you revoke <all_urls>. Check that the interface says access is absent and Start is unavailable.

My old project is missing after updating.

A different unpacked folder can create another extension ID with separate storage. Export JSON from the old installation and import it into the new one. Do not remove the old installation until the import is verified.

Compatibility & limits

  • Russian interface only. Desktop Chrome unpacked extension; no Web Store listing, automatic installation or automatic update.
  • Exact 0.1.3 passed ordinary Chrome 152.0.7977.82/Linux normal installation, permissions, four-page capture, active/paused export blocking, cancellation, CSV/HTML/JSON, immediate reload and revocation. A separate 0.1.2 run passed Chrome for Testing 151/Linux. Windows/macOS, other Chrome versions and 50-page scale remain unverified.
  • Manual URLs from one authorised origin; visible-area screenshots only. No crawl, full-page stitching, automatic grouping or security audit. Timeouts, tab switching, repeated client and agency workflows remain unverified.
  • The included preview permission allows no-charge use, including real workflows, without a key. Purchase supplies the prepared download, illustrated guide and practice bundle; it does not revoke rights in previously obtained copies. Read PREVIEW-PERMISSION.md and third-party notices.
  • A person must review the captured pages, groups, decisions and private content. Exports are not client approval or a guarantee that the website is complete. Local projects are deleted if the extension is removed; keep JSON backups.

Need a hand?

Tell us the product, host application and version, what you tried, and the exact error. Contact support with a fictional example; keep private customer files and passwords out of your message.