A gitingest and Repomix alternative that runs in your browser.
Drop a folder or paste a public GitHub link. The files are read here, lock files and tests stay out by default, PDFs and Word files come in as text, and one file comes back with its token count.
- A folder or ZIP read in your browser
- A GitHub repo fetched straight from GitHub
- No install, no sign-up, nothing uploaded to us
Drop a folder or files
One file comes back, usually in under a second.
Paste a public link
Where gitingest, Repomix and FileConcat process your code.
Each tool in its own words, read on its own pages in September 2026. Both command-line tools run on your machine; the two websites do the work on theirs.
| Tool | Where the work happens | In its words |
|---|---|---|
| FileConcat | In your browser tab. A folder or ZIP is read from your disk, and a public GitHub repository is fetched by your browser straight from GitHub. | Nothing uploaded to us |
| gitingest website | Takes a Git repository link. The repository is cloned on gitingest's backend and deleted after processing. | "Cloned repos are deleted after processing" |
| gitingest command line | On your machine, once installed with pip. | "pip install gitingest" |
| Repomix website | A folder or ZIP you upload is stored on Repomix's servers while it is packed, then deleted. | "your files are temporarily stored on our servers for processing" |
| Repomix command line | On your machine, run with npx. | "Since all processing is local" |
Measured against the tools you would compare it with.
Four tools over the same 60 repositories, each at its own defaults, one tokenizer.
median of the per-repository share
fewer tokens only helps if the dropped file did not matter
in the sample, 7 of 60 checkouts hold a document; only this bundle carries its text
The most aggressive filter of the four. Of a checkout's test tokens the CLI bundle carries a median 15.6% where the other three carry 100%, and nothing under a dot directory. In the browser a held-back file sits in the tree and a tick puts it back.
tests are 47.3% of what Repomix carries and we do not, vendored code 42.7%; hidden source is 0.1% of a checkout's source at p90
When gitingest or Repomix is the better pick.
- You want every test file in.
- Repomix and gitingest keep tests at their defaults. FileConcat leaves files named as tests out until you tick them back in under Adjust what's included.
- The repository is private and you want to paste a link.
- gitingest's site takes a GitHub personal access token. Here, clone the repository and drop the folder instead.
- You work in a terminal or a CI job.
- Both ship a command-line tool that runs on your machine: npx repomix@latest, or pip install gitingest.
- You want Repomix's extras.
- Its guide lists code compression, comment removal and an MCP server, none of which FileConcat has.
Common questions.
- Is there a gitingest alternative that runs locally?
- FileConcat runs in your browser tab: a folder or ZIP is read from your disk, and a public GitHub repository is fetched by your browser straight from GitHub, with nothing to install. gitingest's own command-line tool also runs on your machine, installed with pip.
- Is Repomix safe to use?
- Its privacy policy draws the line itself. The command-line tool processes everything locally, which the policy says makes it safe for private and internal repositories. The website is different for a folder or ZIP: uploaded files are temporarily stored on Repomix's servers and deleted immediately after processing.
- Does gitingest work with private repositories?
- Yes, with a GitHub personal access token, which its site says is used once for cloning and never stored. FileConcat does not import a private repository by link: clone it and drop the folder, which is read in your browser.
- Which one packs the most of my own code?
- Over the same 60 public repositories on 2026-09-10, each tool at its defaults, a FileConcat bundle was a median 68.0% source code, against 51.1% for gitingest and 49.6% for Repomix. Tests alone were a median 9.0% of a gitingest bundle and 9.4% of a Repomix one, against 0.7% of ours.
- Can gitingest or Repomix read PDFs and Word files?
- Not at their defaults in our test on 2026-09-10. Given a folder with a PDF, a Word file, a spreadsheet and a slide deck next to the code, Repomix packed the source file only and gitingest named three of the documents without their text. FileConcat carried the text of all four. Both describe themselves as packing a codebase, and a PDF is not code.
- Is my code uploaded to a server?
- Not to us. A folder is read in your browser tab, and a public repository is fetched by your browser from GitHub, so that request goes to them. There is no account to create.
Try it on your own repository.
The full method and every repository: Repomix vs gitingest vs code2prompt, 60 repositories measured. A repository link in more detail: GitHub repo to text.