Peek inside GitHub files and folders without clicking.
A small Chrome extension born out of pure developer frustration.
Install from the Chrome Web Store
Have you ever been inside a GitHub repository and felt this loop?
You open a file. You go back. You open another file. You go back. Again. And again.
Now add images to the mix.
You can't even see what an image is unless you open it. So you end up opening every single image, one by one, just to figure out which one you want.
This constant back-and-forth is frustrating. Later I learned this behavior is called pogo-sticking — but at that moment, it was just annoying.
I hit this problem while browsing a wallpaper repository. I had to select a few images, and opening each one individually was driving me crazy. I searched for a solution. I didn't find one.
So I decided to build my own.
What if you could just hover over a file in the GitHub file tree and instantly see what's inside?
- Image file → show an image preview
- Code file → show the code (with syntax highlighting)
- Folder → show a mini file tree
- No clicking
- No page navigation
- No losing context
Inspired by Wikipedia-style hover popups, Peek-a-Repo lets you peek inside files before opening them. Worth reading the Wikipedia article where they explain why it took so long to build that tiny link preview on Wikipedia. It's cool to see how much effort went into making that tiny link preview on Wikipedia.
-
Hover previews for images — supports any aspect ratio, scaled by resolution
-
Hover previews for code files — syntax highlighting via Prism.js (JS, TS, HTML, CSS, JSON, Markdown, Rust, Go, Python, and more)
-
Hover previews for folders — mini GitHub-style file tree with folder/file icons; hover files inside to preview them too
-
Nested previews — hover a file inside a folder popup to peek its contents inline
-
Smooth momentum scrolling — velocity-based scroll with decay inside the popup
-
"View more" — expand truncated files without leaving the page
-
Smart caching — repeated hovers are instant, no extra API calls
-
Privacy-first — your GitHub token is stored locally in
chrome.storage, never sent anywhere
The easiest way — install Peek-a-Repo here.
After installing, click the extension icon and sign in with GitHub (one click, uses OAuth device flow). That's it — go to any GitHub repo and start hovering.
-
Clone this repository:
git clone https://github.com/xevrion/peek-a-repo.git
-
Open
chrome://extensions(orbrave://extensions) -
Enable Developer mode (top-right toggle)
-
Click Load unpacked and select the project folder
-
Click the extension icon → sign in with GitHub or paste a Personal Access Token
-
Install dependencies (only Tailwind is needed):
npm install
-
Run Tailwind in watch mode:
npx tailwindcss -i ./input.css -o ./tailwind.css --minify --watch
-
Make changes to the code
-
Reload the extension from
chrome://extensions
Peek-a-Repo does not collect any user data. Your GitHub token is stored locally and only used to make GitHub API requests directly from your browser. See the full privacy policy.
Contributions are welcome! Feel free to open issues or pull requests. Read the contributing guide for more details.
