Remove FBclid and UTM
Removes fbclid and utm_ query parameters in URLs.
Total ratings
4.04
(Rating count:
23)Review summary
These summaries are automatically generated weekly using AI based on recent user reviews.
Chrome Web Store does not verify user reviews, so some user reviews may be inaccurate,
spammy, or outdated. Pros
- Works as expected for removing fbclid and UTM parameters.
- Great extension with minimal code that effectively removes tracking info.
- Generally good performance with most websites.
Cons
- Breaks functionality on certain websites like LinkedIn and Spotify.
- Re-encodes parameters containing UTF-8 characters incorrectly.
- Causes infinite redirect loops when handling spaces in URLs.
- Issues with Brave browser after the latest update, including redirection notices.
Most mentioned
- Breaks some website functionalities.
- Functions well for fbclid and UTM removal.
- Issues with Spotify web player.
- Problems with LinkedIn profile loading.
- Inconsistent handling of URL encoding.
Upgrade to see all 41 reviews
User reviews
Recent rating average:
3.00
All time rating average:
4.04
Upgrade to see all 41 reviews
Rating filters
5 star 4 star
3 star
2 star
1 star
| Date | Author | Rating | Lang | Comment |
|---|---|---|---|---|
| 2024-06-14 |  | | en | it works but occasionally breaks request with query string which is not formatted in key-value pairs. e.g. http://foo/?non_keyvalue_pair_string => Internal Redirect => http://foo/?non_keyvalue_pair_string= |
| 2024-04-22 |  | | en | This is what i need... |
| 2024-01-24 |  | | ||
| 2023-01-26 |  | | It does what it says. BUT, it breaks some websites. Biggest example is LinkedIn. Search, messaging and many other features stop working when this extension is active. | |
| 2023-01-26 |  | | en | It does what it says. BUT, it breaks some websites. Biggest example is LinkedIn. Search, messaging and many other features stop working when this extension is active. |
| 2022-11-10 |  | | It is good in general, but it re-encodes parameters containing UTF-8 chars wrongly. For example: ?query=p%E4ris comes to ?query=p%EF%BF%BDris | |
| 2022-11-10 |  | | en | It is good in general, but it re-encodes parameters containing UTF-8 chars wrongly. For example: ?query=p%E4ris comes to ?query=p%EF%BF%BDris |
| 2022-11-01 |  | | Buggy, it adds an extra equal sign to the URLs with parameters without values, causing errors. | |
| 2022-04-11 |  | | en | Buggy, it adds an extra equal sign to the URLs with parameters without values, causing errors. |
| 2022-07-28 |  | | Works quite good, except one nuisance. If any URL contains spaces encoded as %20, it changes it to +. I frequently use a search engine which demands spaces encoded as %20 and replaces "pluses" with it. This creates infinite loop and I just get too many redirects error in the end. |
Upgrade to see all 41 reviews