Refresh a website icon or screenshot

Request a new local brand asset from the website card.

Last checked 21 August 2026

Use a manual refresh when a website card has a missing, failed, or outdated screenshot or icon. Each action requests only that asset, so choose the one that needs attention.

Request a refresh

  1. Open Websites.
  2. Open the website card's context menu.
  3. Select Refresh Screenshot or Refresh Icon.
  4. Look for the confirmation message:
    • Refreshing the screenshot for example.com...
    • Refreshing the icon for example.com...
  5. Leave TechDash running while the queued work finishes.

The message confirms that TechDash accepted the request. It does not confirm that a new image has already been captured or saved. The card updates automatically when a usable replacement is written.

What each action does

Refresh Screenshot opens the website's configured source page in TechDash's browser. It uses the saved user agent and HTTP Basic Authentication settings, captures a viewport image, and attempts a full-page image after scrolling for lazy-loaded content. If the current display name still equals the hostname, this work can replace that hostname label with a name found on the page. It does not replace any other saved name.

Refresh Icon opens the page to collect icon candidates, then checks favicons, touch icons, Open Graph and schema images, manifest icons, and conventional favicon paths. It saves a normalized PNG when it finds a usable candidate.

If the image does not change

An unchanged image does not necessarily mean the action failed. TechDash protects existing usable files:

  • A failed or blank screenshot does not replace an existing screenshot.
  • An icon refresh that cannot fetch a valid candidate keeps the current icon.
  • The website may serve the same image as before.
  • A cached card URL changes only after TechDash updates the website record.

Open the website overview to compare the full-page screenshot with the card's viewport screenshot. The two surfaces can legitimately show different crops.

When a request does not enter the queue

Brand refresh yields to page monitoring. If the page-check queue is backlogged, TechDash can accept the menu action but defer the brand job so crawls keep priority. A locked or unusable license also prevents the job from being enqueued.

Open Queue Status:

  • If screenshot or icon work is waiting or active, let it finish.
  • If the brand queues are empty but page checks are backlogged, wait for page pressure to fall and request the refresh later.
  • If all queues are empty, confirm that the license is usable. A manual refresh can run for a paused website, although scheduled weekly refresh skips paused websites.

Repeatedly selecting the same action does not make the same queued asset run in parallel.

Fix access before retrying

If the card shows a homepage load or capture error:

  1. Open the website's HTTPS source address in a browser on the same computer.
  2. Confirm the final landing page loads successfully.
  3. On Websites, open the card's context menu and select Edit Website.
  4. Correct the Website address if needed.
  5. Expand Advanced Settings to correct HTTP Basic Authentication or choose a different User agent.
  6. Select Save changes, then request the affected asset again.

HTTP Basic Authentication settings do not complete HTML login forms, SSO, passkeys, or CAPTCHAs.

Automatic refresh and paused websites

Each asset is normally due for refresh once a week. Weekly scheduling skips paused websites. After you unpause a website, TechDash asks the brand scheduler to consider due work again.

A later successful screenshot clears an earlier screenshot-capture error on the website card. An icon-only success does not clear a missing screenshot error.

Expected outcome

A successful screenshot refresh updates the card's viewport image and, when available, the overview's full-page image. A successful icon refresh updates the small website icon. If no acceptable replacement is found, a usable old file remains; if no old file exists, TechDash continues to show its placeholder.

If the page loads normally with the saved access settings, queues are clear, and repeated single refreshes still produce no asset or visible error, open Help & Support. Include the TechDash version, operating system, hostname, requested asset, attempt time with time zone, selected user agent, whether Basic Authentication is configured without its password, and screenshots of the card and Queue Status.

Related articles