v4 is a major architectural refactor. We optimized the overall architecture, fixed multiple issues from v3, and added several practical features to prepare for more powerful capabilities in the future.
Due to the large scale of changes, some users have encountered inconveniences. Below is the current known feedback and how we are handling it:
Some users wish to roll back to v3.2. Please download the package from the link below and install it via the browser’s extension developer mode (PC browsers only: Chrome / Edge / Opera and other Chromium-based browsers):
https://fetchv.net/fetchv_v3.2.zip
If you are unsure how to install it, you can ask an AI the following question:
“How to install a zip extension package in developer mode in Chrome / Edge / Opera? Please give detailed steps.”
Note: v3 used an architecture from years ago. Chrome updates very frequently each year and has gradually deprecated some older APIs. The old architecture could no longer keep up, so we decided to refactor. We will not roll back to the old version in the browser extension stores. v3.2 is only provided as a temporary transition and will no longer be maintained.
Some users reported that filenames become something like 526c97f2-0252-4942-a956-f58def8837bd.mp4.
Cause: Certain download-renaming or download-manager extensions listen to and modify all download behaviors in the browser, overwriting the filename passed by this extension and falling back to the default blob URL name.
Solution: We added filename protection logic in v4.0.3, but it still cannot completely prevent interference from other extensions. In Chrome / Edge, later-installed extensions have higher filename priority. This is a hard browser limitation and cannot be bypassed. If naming fails, the extension will show a prompt. You can click the “Reload” button in the prompt to identify the conflicting extension, temporarily disable it, or reinstall FetchV (so it is installed later and gains higher priority). FetchV only modifies filenames of its own downloads and does not interfere with other extensions.
Why didn’t v3 have this problem?
v3 used <a> tag simulated clicks for downloads and did not use the browser’s native downloads API, so there was no conflict. However, this method has risks with large files, is prone to download failures, and cannot manage download history. Therefore, v4 switched to the native downloads API.
v4 has built-in multi-threaded downloading that automatically adjusts the number of concurrent requests based on actual download conditions. Manual setting is no longer needed. Compared with manual configuration, automatic adjustment is usually more stable and efficient under different network environments and server limits.
It has been added to the download panel in v4.0.2 and later. You can also find the related settings in the extension popup or sidebar.
Most reports are from Popup mode. Please try switching to Sidebar mode first; it works normally in most cases. We are investigating this issue.
This may be due to detection logic issues. Please submit the problematic webpage URL via the feedback form so we can locate and fix it.
This may be caused by compatibility issues with certain special HLS streams. Please submit the problematic webpage URL via the feedback form. In v4.0.2 and later, a conversion engine option has been added. You can choose to enable the v3 conversion engine (better compatibility, but the output file may have audio/video desync or stuttering). Users can choose according to their needs.
v4 made significant adjustments to the interface and interactions, so some adaptation time is needed. We will continue to optimize based on your actual feedback. If you find specific parts awkward, please tell us directly.
To support more complete features and future extensibility, this version requests additional permissions. These permissions are used only for implementing features and will not be used for other purposes.
We will continue to fix issues based on user feedback and release more fix versions as soon as possible.
If you encounter other issues while using the extension, or have specific suggestions about the interface, please submit them via the feedback form:
https://fetchv.net/zh/feedback
Your feedback is very important to us. Thank you for your understanding and support!