Webflow’s Wishlist remains online despite inactivity, leading users to question its purpose and why feature requests appear to be ignored.
1. Historical Intent of the Wishlist
- Webflow introduced the Wishlist (wishlist.webflow.com) as a centralized place for users to submit, upvote, and track feature requests.
- Its goal was to promote community transparency and give users the sense their voices were being heard and prioritized.
2. Decline in Responsiveness Since 2018
- User comments and upvote activity have continued, but official responses from Webflow became infrequent starting around late 2018.
- Major user-requested features (e.g., native multi-language support, CMS API improvements, pagination beyond collection limits) remained "Under Review" or unaddressed for years, despite high vote counts.
3. Possible Reasons Webflow Keeps It
- Historical transparency: Removing the Wishlist might be perceived as hiding user demand or undermining community trust further.
- Internal roadmapping may have changed, but the platform has never formally deprecated the Wishlist or given users a new venue for public feedback.
- SEO value and inbound traffic: The Wishlist still receives organic traffic from search engines for feature requests, acting as a passive support channel.
- It serves as a living archive of what the community has asked for—even if it's no longer actively curated.
4. Where Webflow Takes Feedback Now
- Enterprise and paid support channels likely receive more responsive feedback loops.
- Community forums and Discord gain more attention from Webflow team members than the Wishlist itself.
- Webflow has focused on product announcements via quarterly livestreams and changelogs, often without referencing Wishlist item statuses.
Summary
Webflow retains the Wishlist likely for transparency and archival reasons, even though it no longer appears to be an active part of their product feedback loop. Users seeking real engagement should use official forums, Discord, or customer support channels instead.