redfetch
RedGIFs media utility

Get the video in the right quality.

Paste a RedGIFs URL or use Batch mode to query several videos at once.

Forces Strong blur and hides IDs and social metadata on screen. Works in both Individual and Batch modes.
FAQ

Frequently asked questions

What does RedFetch do?
RedFetch finds the available media versions for one or multiple RedGIFs videos and brings them together in one place, with a preview, HD and SD options, size, duration and, when available, creator, post date, views and likes.
Why use RedFetch instead of downloading through RedGIFs?
RedFetch makes the process more direct: paste a link and get the available HD and SD versions, preview, size, duration and public metadata in one interface. RedFetch does not recompress video files; it uses the media URLs provided by RedGIFs.
What is the difference between HD and SD?
HD offers the best available quality and usually produces a larger file. SD uses a lighter version of the video and takes up less space.
What is “GitHub Web — 25 MiB”?
It is an optional Batch-mode check. It compares the HD and SD sizes already obtained by RedFetch with the 25 MiB per-file limit currently documented by GitHub for files added to a repository in the browser. RedFetch does not send files or queries to GitHub for this check. Other GitHub upload methods have different limits.
Why might a video not work?
The video may have been removed, the link may be incorrect, or RedGIFs may be temporarily unavailable. Changes to the service itself can also affect media availability.
Does RedFetch store the videos?
HD and SD video files are not hosted or stored by RedFetch. The backend queries RedGIFs metadata, checks the remote file size and may fetch a preview image, temporarily converting it to a data URI. When you open HD or SD, your browser accesses the media on the host provided by RedGIFs.
What is Portable history?
It is an optional Batch-mode .log file that records previously queried IDs, dates, query count and HD/SD availability. New entries can also keep an optional snapshot of creator, post date, views and likes; older history files remain compatible. When you import the file later, RedFetch recognizes repeated IDs and lets you put them back in the queue, remove them before searching, or skip new requests. History records queries; it does not confirm that a video was downloaded.
Can I use history to keep IDs and query them later?
Yes. After importing the .log file, use “Add from history to queue”. The IDs return to the Batch queue, but no request is made until you tap “Search videos”. If the history contains more than 100 IDs, RedFetch restores them in batches and, in this tab, continues from where it stopped after “New search”.
Can I name and describe a history file?
Yes. Name and description are optional and can be edited with the pencil icon. If the name is empty, the interface uses “Portable history”; if the description is empty, no extra line appears. This information follows future revisions of the same family inside the .log file.
What do v1, v2 and v3 mean in the history file?
They are cumulative revisions of the same history family. The first file starts at v1; if it is imported, receives new queries and is exported again, it becomes v2, then v3, and so on. The date/time portion of the filename identifies the original family, so a separate history starts with a different timestamp and returns to v1. Name and description, when used, stay with that family. This is different from FORMAT_VERSION, which is only the technical version of the file structure.
Why can Export be disabled?
To avoid creating v2, v3 or v4 just because a previously known video was queried again. After importing or exporting a revision, re-querying existing IDs may update COUNT, LAST_SEEN, status and metadata in the tab, but it does not unlock another revision. The next revision is only unlocked when at least one new ID is added to history. Name and description are also kept in the tab and included in that next revision. After an export is requested, the same revision remains available under “Download again”, because the browser does not tell RedFetch whether you completed saving the file to your device.
Is the history file sent to any server?
No. The import is read locally by JavaScript in your browser. The .log file — including an optional name and description — is not sent to the RedFetch backend, Vercel, RedGIFs or any other service by this feature. The history remains only in the tab memory until you reload, close or clear the session; the persistent copy is the file you choose to export to your device.