DatafetchPro
Start a project

Services

ServicesHow it worksWork together

Explore

BlogPast workPortfolioFAQCommunityToolsAutomationCourses
Log in

Tools · free & browser-based

The data tooldesk

Small, single-purpose tools for pulling data out of the web and getting it into a shape you can use. Run one, read the result on screen, then take the whole set with you in whichever format your pipeline eats. Everything runs server-side against a self-hosted backend — no signup, no keys in the browser.

Checking backend…9 export formats2 tools

YouTube comments

Threaded comments, likes, pins and hearts

Paste a watch URL, a Shorts link or a bare video ID and pull back up to 50 comments with their replies, like counts, creator hearts and pinned flags.

  • Up to 50 per run
  • Replies nested
  • Creator + pinned flags
POST /api/tools/youtube-comments

TikTok comments

Paged comments with replies and proxy rotation

Full URLs, vm/vt share links or numeric IDs. Pages through comments and replies with configurable retries, pacing and a rotating proxy pool.

  • Up to 100 per run
  • Reply limit per thread
  • Proxy pool + retries
POST /api/tools/tiktok-comments

Export in any shape

Every tool shares one export dock: pick a format, preview the exact bytes, then download or copy. Filtered views export on their own.

  • .csv
  • .xls
  • .tsv
  • .json
  • .jsonl
  • .xml
  • .md
  • .html
  • .txt

How a run works

Four moves, start to export

  1. Give it a target

    A URL, a share link or a bare ID — each tool normalises what you paste.

  2. Tune the run

    Limits, depth, fingerprint, retries, pacing and proxies where they apply.

  3. Read the result

    A structured view, a sortable table, or the raw JSON the backend sent.

  4. Export anywhere

    CSV, Excel, TSV, JSON, JSONL, XML, Markdown, HTML or text.

Self-hosted backend

The tool pages never talk to a scraper directly. They POST to /api/tools/*, which validates the input and forwards it to the FastAPI service at TOOLS_API_URL. Point that variable at whichever host and port the service listens on — it stays server-side, so the backend can live on localhost without ever being exposed.