tallshot

Support

Something not working, or an idea for what Tallshot should do next? Both are welcome. Tallshot is built and maintained by one person, so replies come from a human, usually within a few days.

Email

Best for anything — bugs, questions, feature requests.

suchartmart@gmail.com

GitHub issues

If you have a GitHub account and want to track the fix publicly.

Open an issue ↗

Reporting a bug

Including these five things usually turns a two-week back-and-forth into a single reply:

  1. What you were trying to capture — the page's address, or the kind of page if it is private
  2. Which capture you used: current tab, full page, or screen/window
  3. What happened, and what you expected instead
  4. Your Chrome version (chrome://version) and operating system
  5. The Tallshot version, shown at the bottom of the sidebar in Capture history
Please do not send screenshots containing information you would not want a stranger to see. If a capture is the only way to show the bug, use Tallshot's Redact tool on it first.

Common questions

Full-page capture says the page cannot be scrolled further

Some pages do not let an extension scroll them — Chrome's own pages (chrome://…), the built-in PDF viewer, and the Chrome Web Store are the usual ones. Use Capture current tab on those instead.

If it happens on an ordinary website, it is often a page that scrolls inside its own box rather than scrolling the document. Try zooming out one step and capturing again, and let me know the address so I can look at it.

Part of a long page is missing from the capture

Full-page capture is capped at 32,760 pixels per side and 100 million pixels in total. Beyond that, zoom out and capture again. Infinite-scroll feeds can exceed the limit no matter what.

Pages that load content very slowly, or that rearrange themselves while scrolling, may also come out incomplete. Scrolling to the bottom once yourself before capturing often fixes it, because the content is then already loaded.

Auto-download keeps opening a save dialog, or fails

Chrome's own setting takes priority over Tallshot's. Open chrome://settings/downloads and turn off Ask where to save each file before downloading. With that on, automatic downloads cannot complete without your input.

Screen or window capture does nothing on macOS

macOS requires Chrome itself to hold the Screen Recording permission. Open System Settings → Privacy & Security → Screen Recording, switch Chrome on, then quit and reopen Chrome. This is a macOS permission granted to the browser, not to Tallshot.

A pasted capture is cut off in Google Docs

Google Docs rejects or truncates very large images. Tallshot downscales copies above 25,000,000 pixels by default — the Fit copies to Google Docs limits setting. If it still gets cut, crop the capture smaller in the editor, or download it as a file and insert that instead.

Where are my captures stored, and can I get them back?

In the browser profile on the computer you took them with, never on a server. They are not synced to your Google account or to your other devices, and there is no backup to restore from.

Uninstalling the extension deletes them along with it. Download anything you want to keep before uninstalling — downloaded files are ordinary files and are never touched by Tallshot.

Text in the exported PDF is not selectable

A screenshot is an image, and the PDF embeds that image. There is no OCR step, so the words inside it are pixels rather than text. Smart page splitting only chooses where to break between pages; it does not read the content.

Can I redact something and be sure it is really gone?

Yes, once you save. Redaction draws an opaque block, and Save changes flattens it into a new image that replaces the original in your history — the covered pixels are discarded, not hidden under a layer. Before you save, Undo and Erase can still bring them back, which is the point of having them.

Does Tallshot send my screenshots anywhere?

No. It has no server and makes no network requests at all. Everything — capture, editing, PDF export — happens in your browser. The full details are in the privacy policy.

Feature requests

Tell me what you were trying to do, not just what to build — the underlying task usually suggests a better feature than the one either of us thought of first. Email or an issue both work.