ReelDown input guide · public-source boundaries

Supported URLs & Inputs

ReelDown uses different input types for different workflows. Some tools are designed around direct public Instagram or Threads links, while other pages work conceptually with a username, hashtag, topic or account-owned follower data. This guide helps you choose the right ReelDown page without treating every task as the same kind of URL.

✓ Public-source workflows ✓ No private-access bypass ✓ Task-specific routing

This is a support and navigation page. It documents the input families that current ReelDown workflows are designed around. Interactive processing may still depend on the implementation status of the individual tool.

Direct media links

Instagram Content URLs

When your task starts from one specific public Instagram item, use the page that matches the content type or the action you want to perform.

Standard Instagram feed post Use the broad post workflow when the public feed item itself is the starting point and its media type may vary.

Post Downloader →

Instagram Reel Use the dedicated Reel workflow when the source is a public Reel rather than a standard feed-post task.

Reels Downloader →

Instagram Story Story availability can change because Stories are temporary or may no longer be publicly available.

Story Downloader →

Instagram Highlight Use the Highlight workflow when the task is about media available from a supported public Highlight source.

Highlight Downloader →

Media-specific tasks

Choose the Output You Actually Need

The same feed item can sometimes contain different media. ReelDown keeps several format-specific workflows separate so a broad post task does not replace a more precise image, video or multi-item task.

Single public image Use the photo workflow when the required source media is an available image from a supported public photo post.

Photo Downloader →

Public feed video Use the video workflow for a supported public Instagram video-post source rather than a Reel-specific task.

Video Downloader →

Multiple media items Multi-item posts need a carousel-oriented workflow rather than treating only the first available item as the post.

Carousel Downloader →

Available audio Audio is a separate output task and availability depends on the supported public media source and finished backend.

Audio Workflow →

Follower/following comparison Designed around comparing relevant follower and following information without presenting it as a public-media URL task.

Followers Checker →

Unfollower comparison Use the unfollower workflow for follow-back and unfollower comparison rather than general follower counting.

Unfollowers →

Account-owned follower export Export intent is documented separately and should use account-owned data rather than claiming hidden public access.

Follower Export →

Hashtags and topics

Hashtag Inputs Are Not Media URLs

A hashtag query or topic idea belongs to a different workflow from a direct Instagram content URL.

Hashtag search

Use the hashtag-search page for supported tag lookup and search intent without mixing in tagged-profile content or analytics.

Hashtag Search →

Hashtag generation

Use the generator when the input is a topic, niche or post idea and the goal is to produce relevant hashtag suggestions.

Hashtag Generator →

Tagged profile content

Tagged posts and photos associated with a public profile belong to the tagged-content viewing workflow instead.

Tagged Viewer →

Threads

Supported Public Threads Post Links

ReelDown keeps Threads separate from Instagram media workflows. The current Threads page is designed around supported public Threads post links and available video media without claiming separate photo or image-specific functionality.

✓ Public Threads post scope

✓ Video-media scope documented

✓ No private-access bypass

✓ Separate from Instagram URLs

Important limits

What a Supported Input Does Not Guarantee

A correctly shaped URL, username or query does not guarantee that a source is still available or that a specific media rendition can be returned.

Private or restricted access

ReelDown does not document private-account bypassing as a supported workflow. Relevant information must already be available through the supported source or account-owned data.

Deleted, expired or changed content

Public availability can change. Stories can expire, posts can be deleted and account visibility can change after a link was shared.

Output depends on implementation and source

ReelDown does not promise a media format, resolution, historical dataset or live result that the completed workflow and supported source have not actually verified.

Facebook inputs

Supported Facebook URL Types

ReelDown separates traditional Facebook video URLs from Facebook Reel URLs. Both current Facebook pages are preview/documentation routes while interactive Facebook processing remains inactive.

Public Facebook video URL

Use the exact public URL of an individual Facebook video for the Facebook Video Downloader page. Private-access bypassing is not supported.

Public Facebook Reel URL

Use the exact public Reel URL for the Facebook Reel Downloader . Reel intent stays separate from ordinary Facebook video posts.

Current implementation status

Facebook pages currently document supported public-link scope, limits and planned behavior. A visible page does not mean the interactive backend is already active.

Pinterest inputs

Supported Pinterest URL Types

ReelDown separates public Pinterest Video Pin URLs from public Pinterest image Pin URLs. Video and still-image intent use different dedicated preview pages while interactive processing remains inactive.

Public Pinterest Video Pin

Use an individual public Video Pin URL for the Pinterest Video Downloader .

Public Pinterest image Pin

Use an individual public image or photo Pin URL for the Pinterest Image Downloader .

Boards and profiles are different inputs

A board, profile or Pinterest search-results page does not identify the same single media source as an individual Pin.

Current implementation status

Interactive Pinterest downloading is not active yet. Private-access bypassing is not supported.

FAQ

Supported URLs and Inputs FAQ

Quick answers for choosing the correct ReelDown workflow.

Does every ReelDown tool require an Instagram URL?

No. Media-oriented workflows can start from a supported public content link, while other pages are designed around usernames, hashtags, topics, public account information or account-owned follower data.

Which page should I use for a normal Instagram post?

Use the Post Downloader for broad feed-post download intent. If you already know you need one specific image, video or a multi-item carousel, use the matching media-specific page.

Are Reels and standard feed posts the same workflow?

No. ReelDown keeps Reel-specific intent separate from standard feed-post intent so the two tasks do not compete for the same page purpose.

Can ReelDown use private Instagram links?

ReelDown does not treat private-access bypassing as a supported workflow. Public-source and account-owned data boundaries apply.

Why are follower tools separate from media downloaders?

Follower comparison, recent-follow information, counts and account-owned exports use different data and answer different tasks from downloading media attached to one public post.

Does a supported URL guarantee a downloadable result?

No. Availability can depend on the source, content visibility, media type and the implementation status of the individual ReelDown workflow.