PixelGhostChrome extension · v3.0
← PixelGhost

PixelGhost /Support & issues

Let’s sortit out.

PixelGhost support happens in the open, on GitHub Issues. Bug reports, questions and suggestions live in the public PixelGhost repository — so a fix or workaround found once can help everyone who runs into the same thing.

Go to GitHub IssuesCheck before you report
Where reports goAbhishekSRajput / pixelghostgithub.com/AbhishekSRajput/pixelghost/issuesReport a bugSomething broke or behaves oddly.Get helpNot sure how something works.SuggestAn improvement worth making.

01 /How reporting works

Four steps. One thread.

Each problem gets a single public issue. Updates, fixes and workarounds are posted there.

  1. 01

    Rule out the page

    PixelGhost works on ordinary http:// and https:// pages. Reload a supported page and try the action again.

  2. 02

    Search existing issues

    Someone may have reported it already. If so, add what you are seeing to that issue instead of starting a new one.

    Search issues
  3. 03

    Open a new issue

    Describe the problem with the details listed below. Keep private images, URLs and data out — issues are public.

    New issue
  4. 04

    Follow the thread

    Questions and fixes are answered on the issue itself. Subscribe on GitHub to be notified when it changes.

02 /Before opening an issue

Three quick checks.

Most surprises come from the page, the shortcut or the site’s framing rules. These take a minute.

Supported pages

Browser-internal pages, extension stores and other restricted pages do not allow extensions to inject overlays. If the affected page is supported, reload it and try the action again before reporting.

Keyboard shortcuts

Check the widget toggle in Chrome’s extension shortcut settings: Alt+Shift+G is the suggested default and may be unassigned if it conflicts with another shortcut. Color and capture shortcuts need their tools open.

Shortcut guide

Device previews

Previews load the site in frames and can be limited by its framing rules. Say whether Allow framing, High fidelity or Stay on after reload was on. Previews use your desktop browser’s engine.

03 /What to include

A good report travels fast.

  • The PixelGhost version and Chrome version.
  • Clear steps to reproduce the problem.
  • What you expected and what happened instead.
  • The affected tool: Layers, Color, Ruler, Inspector, Screenshot, its editor or Steps, Devices, Element Selector, Assets, Vision, SEO, or Stack.
  • Whether the popup or side panel was open, and whether reloading the page changes the result. For keyboard issues, your operating system.
  • Screenshots or error messages, if they are safe to share.

Issue outlineMarkdown

**PixelGhost version:**
**Chrome version:**
**Tool:** Layers / Screenshot / Devices / …
**Popup or side panel open:** yes / no

### Steps to reproduce
1.
2.

### Expected

### What happened
Paste this into a new issue and fill it in

04 /Privacy and security

Issues are public.

Anyone can read a GitHub issue. Crop or redact anything you choose to share.

Keep out of GitHub

Private overlay images, captures or recordings, audit exports, sensitive page URLs, personal information, or other confidential data.

Email instead

Privacy requests, security reports, or support that requires private details.

codecube99@gmail.com

05 /Quick answers

Maybe it’s one of these.

Still stuck? Open an issue on GitHub.

Why doesn’t PixelGhost run on every page?

PixelGhost works on ordinary HTTP and HTTPS pages. Browser-internal pages, extension stores and other restricted pages do not allow overlays. On a supported page, reload and try the action again.

Alt+Shift+G doesn’t do anything.

The shortcut can be unassigned if another extension uses it, so check Chrome’s extension shortcut settings. It also does nothing before first-use consent or on a browser-restricted page.

Do I need an overlay to use the inspection tools?

No. Open a supported page and launch a tool from the popup’s TOOLS section or the icon rail in the on-page widget. The inspection tools work without an overlay layer.

Why did my overlay disappear when I opened a tool?

Color Picker and Element Selector temporarily stand overlay layers aside so they read the page itself. Inspector does the same by default; Show design keeps the reference visible. Page Ruler keeps the overlay visible, and Screenshot lets you choose whether to include it.

A site won’t load in the Device Simulator.

Sites that refuse framing with X-Frame-Options can still be previewed. A site whose Content-Security-Policy refuses offers Allow framing. That exception applies only to the page’s exact origin in this tab, until the simulator closes.

Do I have to allow clipboard access?

No. The Paste button asks for optional clipboard-read permission when you select it. You can decline and use local files, a folder, an HTTPS image URL, or ordinary Ctrl+V paste instead.

Where do my screenshots go?

Only where you send them: a file you save or the clipboard you copy to. Recent keeps your last twelve on your device so you can copy or save them again; Clear all deletes them. Captures are never uploaded.