Free tool
Duplicate feature request finder
Nothing leaves your browser. The list is grouped on this page and never uploaded.
How it works
Each request is cleaned up first: lowercased, filler words like “please” and “add” removed, and common synonyms folded together, so “dark theme”, “night mode” and “dark mode” read as one idea.
Then every pair of requests gets a similarity score. Words that only a few requests use count for more than words that appear everywhere, a short request that sits inside a longer one counts as a match, and letter patterns catch typos and different word forms.
Pairs above the sensitivity you choose are joined into groups. The request that is most similar to the rest of its group becomes the suggested title. That’s usually the clearest wording to keep when you merge.
Merge the duplicates in your own tool and keep each one as a vote, so the count reflects everyone who asked. The guide to duplicate feature requests covers how to merge without losing voters.
FAQ
Is my list uploaded anywhere?
How does it decide two requests are duplicates?
Which sensitivity should I use?
Can I use an export from Canny, Featurebase or a spreadsheet?
How is this different from what Sikia does?
Related guides
- GuideHow to handle duplicate feature requestsSpot duplicates across channels, decide when two asks are the same, and merge them without losing voters.
- GuideHow to collect feature requests from Discord without losing themOne channel, a weekly triage habit, and a board people can vote on.
- GuideHow to prioritize feature requests: votes, RICE and revenueWhat each signal tells you, and how to combine them into a decision.
Other free tools
- Free toolRICE prioritization calculatorScore requests by reach, impact, confidence and effort. Rank them and export a CSV.
- Free toolRelease notes writerTurn PR titles and commit messages into release notes users can read.
- Free toolFeedback tool cost calculatorSee what Canny, Featurebase, Frill, Nolt, Upvoty, UserJot and Sikia cost for your team.