How to Report a Bug in Edge Drop
Report Edge Drop bugs on the project's GitHub Issues page, using the Report a Bug template. You can get there from the app: open Settings from the tray icon and select Submit Feedback in the About Edge-Drop card. A report that includes your Edge Drop version, which build you installed, your Windows version, your display setup and exact steps to reproduce the problem is far easier to fix than "the shelf doesn't open sometimes".
Where to report Edge Drop bugs
Issues on the Edge Drop repository must be opened from one of three templates (blank issues are turned off):
| Template | Use it for | Title starts with |
|---|---|---|
| Report a Bug | Something broken, a crash, or wrong behaviour | [BUG]: |
| Request a Feature | Something Edge Drop doesn't do yet | [FEATURE]: |
| Feedback & Thoughts | General comments and suggestions | [FEEDBACK]: |
To file a bug:
- Open the Edge Drop issues page on GitHub, or select Submit Feedback in Edge Drop's Settings.
- Search the existing issues for your symptom first. If someone has already reported it, add your details as a comment instead of opening a duplicate.
- Select New issue and choose Report a Bug.
- Replace the placeholder after
[BUG]:with a short, specific title. - Fill in the description (the template below covers what to include) and submit.
You need a GitHub account to open or comment on an issue. Issues are public, so anyone can read what you post. A clear report is also one of the most useful ways to support Edge Drop without paying.
Information to gather before you file
Edge Drop version and build
Open Settings and scroll to the bottom of any tab. The About Edge-Drop card shows your version number. Then note which build you have:
- GitHub installer: the Behaviour tab has an Updates section, and the Community & Support card shows Star on GitHub.
- Microsoft Store: there's no Updates section, and the Community & Support card shows Review on Microsoft Store.
The two builds differ in how they update and where Windows keeps their files, so this detail matters. If you're not on the latest version, check the changelog first, since the bug may already be fixed.
Windows version
Select Start > Settings > System > About and look under Windows specifications for the edition, version and OS build. Copy those three lines into your report.
Display setup
Many shelf problems depend on the screen layout, so include:
- the number of monitors, and which one Edge Drop uses (Display Screen on the Position tab),
- each monitor's resolution and scale (from Settings > System > Display),
- which edge the shelf is on (Edge Placement: Left, Top or Right).
Settings that change behaviour
Mention any of these that aren't at their defaults: Hover Activation, Fullscreen Protection, Open Delay, Incognito mode, Global Toggle Shortcut, Hover area size and Edge trigger thickness. Edge Drop's settings, tab by tab lists every default.
What you copied, and from where
For capture or paste problems, name the app you copied from and what kind of content it was: plain text, formatted text from a browser or Word, a screenshot, files from File Explorer, a spreadsheet range, or a colour code. The project's README specifically asks for reports about content Edge Drop puts in the wrong category, with the source app named. Describe the content rather than pasting it if it's private.
Other clipboard tools
Say whether Ditto, CopyQ, Windows clipboard history (Win+V) or another clipboard tool is running at the same time. Two clipboard tools can interfere with each other; two clipboard managers fighting explains how.
Write steps someone else can repeat
The most useful part of a report is a short sequence that makes the bug happen:
- Start from a known state. For example: "Edge Drop just launched, shelf on the right edge, default settings."
- Be exact about each action. "Copy two PNG files in File Explorer" is reproducible; "copy some stuff" isn't.
- Say how often it happens. "Every time", "about 1 in 5 tries" or "once a day after the PC wakes from sleep" all help.
- Describe what you saw, not what you think caused it. Expected versus actual behaviour is enough.
- Report one bug per issue. Two problems in one issue are hard to track and close.
A screenshot or short screen recording helps with visual problems. GitHub lets you attach files by dragging them into the comment box. Check that nothing private is visible before you upload it.
A bug report template you can copy
Edge Drop version: 0.4.0
Build: GitHub installer / Microsoft Store
Windows: (edition, version, OS build from Settings > System > About)
Displays: (number of monitors, resolution and scale; which one Edge Drop uses)
Shelf edge: Left / Top / Right
Changed settings: (anything not at its default)
Other clipboard tools running: (Ditto, CopyQ, Win+V, none)
What I did:
1.
2.
3.
What I expected:
What happened instead:
How often: (every time / sometimes / once)
Content involved: (text, formatted text, image, files, colour code; source app)
What not to include
Bug reports are public and indexed by search engines. Leave out:
- passwords, tokens, API keys or anything else copied from a password manager,
- customer data, personal messages, or internal links,
- files from Edge Drop's data folder. The history index is encrypted to your Windows account, but saved images and long text clips are ordinary files that may contain private content.
If the bug involves sensitive content, describe its type and size instead ("a 2,000-line text file", "a 4K screenshot").
Before you file: two quick checks
- Restart Edge Drop. Right-click the tray icon, select Quit Edge-Drop, and start it again from the Start menu. Note in the report whether the problem came back.
- Update to the latest version. On the GitHub build, use Check for updates in Settings. On the Store build, check for updates in the Microsoft Store.
If the problem seems to involve another program, Safe Mode and a clean boot can show whether something else on the PC is the cause.
FAQ
Can I report an Edge Drop bug without a GitHub account?
GitHub Issues is the channel the app links to, and it needs a free GitHub account. Microsoft Store reviews are visible to other users, but they aren't a bug tracker.
Where are Edge Drop's log files?
Edge Drop doesn't write log files for you to attach. Your steps, version details and a screenshot or recording do that job.
How do I request a new feature?
Use the Request a Feature template on the same Issues page. For larger changes, the README asks you to open an issue to discuss the scope before sending code.
Related reading
- Edge Drop Changelog: What's New and Where to Find It
- How Edge Drop Updates: GitHub Build vs Microsoft Store
- Where Edge Drop Stores Data on Disk
- How to Build Edge Drop From Source on Windows
Sources
- Edge Drop issues (GitHub) — the issue tracker and its templates.
- Edge Drop README (GitHub) — what the project asks bug reporters to include.
- Creating an issue (GitHub Docs) — opening an issue from a template.
- Find information about your Windows device (Microsoft Support) — finding the Windows edition and version in Settings > System > About.
Deepender Yadav created Edge Drop and builds and tests it, from the edge-hover shelf to each release. A B.Tech Computer Science Engineering student, Deepender writes the Edge Drop guides, comparisons and developer posts, and checks product details against the app's source code.
GitHub · LinkedInCopy. Stack. Drop.
Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.
Download for Windows Get from Microsoft Store
How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge Drop vs Win+V · Support
Free · Lightweight · Privacy First