FileConcat Clipper: threads, chats and transcripts to Markdown

FileConcat Clipper turns what you are reading into Markdown files and hands them to an open fileconcat.com tab, where they join a bundle you can copy or download in one piece. It is for anyone who assembles reading material for an LLM and is tired of pasting pages in one at a time. Copying a page into Markdown is the easy half. What is hard to get out of a browser is a discussion, and that is what this is built around. WHAT IT CLIPS Reddit threads, whole. The post and its comments, with every author, score and level of nesting kept, so a reply reads as a reply to the thing above it rather than as one more paragraph. "Expand more comments" clicks the thread's own "more replies" three rounds deep, and it is off by default because it is slower. ChatGPT, Claude and Gemini conversations, whole. The page shows a window of the conversation; the extension reads it the way the site's own client does, one or two same-origin requests on the page's own session. Files a Claude or Gemini conversation wrote come along as files. Listings, one item at a time. A subreddit, a YouTube channel, a front page or a search page lists what it has loaded, and one button scrolls the page for the rest so the whole listing is on offer. Tap a row to clip it, or press Select to take a batch. Each item is opened and read on its own, so a session of scrolling becomes a set of files rather than one flattened page of headlines. YouTube transcripts. A watch page gives you the video's description and its full transcript, which is not text that was on the page to begin with. A channel's Playlists tab lists its playlists, and clipping one clips the videos it holds. Comments are an opt-in extra, off by default: they add the top 60 threads and, under the ones with the most replies, the replies themselves, which runs three to four times the tokens. Any article. Everywhere else, if a page reads as an article, the panel offers to clip it. Mozilla's Readability picks the body and Turndown renders it, which covers newsletters, documentation sites, news and blogs with no per-site code. Navigation, sidebars, cookie bars and footers are left behind. The full list of sites it reads, and what each one gives you, is at fileconcat.com/clipper. HOW IT WORKS Open the side panel from the toolbar icon. It stays open while you browse and re-reads the current tab on every navigation, so it always describes the page in front of you. Clip what you want. A tapped row says it is being read and each clipping lands in a cart, one row per item, so a page that fails says so on its own row and names the reason while the rest carry on. The cart holds the last 50, and the work runs in the background, so closing the panel mid-batch does not stop it. Then press Send. Every finished row goes into your fileconcat.com tab at once, opening one if there is none. A send adds to the bundle rather than replacing it, and files with the same name replace each other, so a repository and the discussion about it can sit in one bundle and re-sending a corrected clipping fixes it in place. What you have sent stays listed for seven days, grouped by send, so you can read a file back or send a whole batch again. It is a receipt rather than a library: the rows drop off on their own, and one button clears them early. WHAT IT DOES NOT DO Nothing is read from a page until you ask for it. There is no background crawling, no page is touched because you happened to visit it, and no clipping is sent anywhere except the fileconcat.com tab you are looking at. There is no account, no sign-in, and no server of ours in the path. Clippings are held in your browser's own storage between the clip and the send. OPEN SOURCE The extension and the site are both at github.com/CeamKrier/file-concat.