Token counter
Exact GPT-4o token counts, per-model cost, and how much of each context window a prompt actually fills.
Pre-launch · 18 free tools, no account
FlexContext turns documents, web searches, websites, videos and datasets into persistent, source-backed knowledge — so a research project accumulates instead of restarting in a new chat every morning.
Say it the way you would say it to a person. Your words are matched to one of 18 tools by readable rules, and the tool runs right here in your browser. No upload, no account.
The workspace is not open yet. Try the free tools and labs in this tab, including a voice studio and a document chat that run their models on your own device.
Free, forever, no account
The same operations FlexContext runs internally, given away as standalone tools. Every one of them opens in your browser and processes your files locally, including the text-to-speech studio. Each has its own page if you want the detail.
Count tokens, split documents, and watch a retrieval ranking explain itself — the mechanics behind every RAG pipeline.
Exact GPT-4o token counts, per-model cost, and how much of each context window a prompt actually fills.
Compare fixed, sentence and Markdown splitting on your own text, with every chunk drawn to scale.
A BM25 ranking with the arithmetic left visible: chunk map, term stats and per-term score contributions.
Cited answers from your own PDFs and Word files, written by an open model running on your graphics card.
The sentences that carry a document, with their pages, or a table told in a few lines. Nothing is reworded or uploaded.
Summaries, tables, JSON and images, combined into one printable HTML page and a Markdown copy.
Profile, filter, convert and validate the files research actually arrives in: CSV, JSON, TSV and plain text.
Column types, nulls, uniques, distributions and correlations from a CSV, in one pass.
Select columns, filter rows, group by a field, aggregate a metric and chart the result.
Move a table between CSV, TSV and JSON, or encode and decode Base64, then download it.
Validate and format JSON, browse its shape, and get the exact line and column of any fault.
Turn pages, images and PDFs into something you can read, cite and reuse.
Turn text into natural speech with Kokoro, running in your browser. Save your favourite voice presets.
Readable text, every link and any tables, pulled out of a page’s HTML source.
Change format, dimensions and quality, compare the file size, and download — without uploading.
Merge documents, extract page ranges, reorder and rotate — on a PDF that never leaves your machine.
Interactive models of the algorithms behind search, ranking and research agents.
Turn the dials a deep-research agent actually has and watch coverage, cost and confidence move.
Describe a link graph, set the damping factor, and watch authority converge iteration by iteration.
Run breadth-first and depth-first traversal over the same graph and compare the journeys.
Build a prefix tree from your own vocabulary and follow autocomplete narrowing, character by character.
Why it exists
Research is not a single question. It is a body of material that should get more valuable each time you return to it — and in a chat window, it does the opposite.
Documents, scanned PDFs, web pages, search results, YouTube transcripts and datasets land in one project instead of six browser tabs.
Claims get attached to the passage they came from, contradictions between sources become visible rather than averaged away.
Notes, annotations, entities and datasets accumulate into a project that is worth more in month three than it was in week one.
Cited reports, structured datasets and — further out — dashboards, knowledge graphs and explainer video from the same material.
What we are building
FlexContext is a workspace where sources, tools and conversation live together — and where you can always see exactly what the model was given.
Documents, images and video in your own space, browsable as a file tree. Every type opens in place — PDF, video, images and agent output.
Answers cite your sources, and clicking one opens the actual PDF or Markdown at the chunk it came from — not a paraphrase of it.
Crawling, media work and analysis run in a bounded sandbox — a fixed core and memory ceiling per job, enforced by the OS, with the CPU cost reported back to you.
A tool run is not a disposable message. It keeps its settings and its result as a block you can read later, or clone into a new run with one click.
Call any tool with / from the composer. Save a configuration you use often as your own command and it is there next time.
It answers on what you selected, and it cannot reach your filesystem or run anything unasked. When a tool would help, it suggests the command — you decide.
Who it is for
Anyone whose output depends on sources they have to keep, compare and cite.
Market sizing, competitive intelligence and due diligence, where the deliverable is only as good as the sources behind it and every figure has to be traceable.
Document sets that grow for months, contradictory sources that need comparing rather than blending, and citations that must survive a fact-check.
Continuous competitor, pricing and customer research that accumulates into something the whole team can query instead of one person’s notebook.
SERP behaviour, ranking structure, internal linking and content research — several of the labs on this page exist because that work needed them.
Literature that has to be read, cited and returned to, with the reading of month one still usable in month six.
Chunking, retrieval, context budgets and evaluation — the tools on this page are the same operations, exposed rather than hidden.
FlexContext is in active development. Rather than collect your email for a launch with no date, the tools above are simply free to use right now, with no account. Here is where things honestly stand.
Questions
An AI research and intelligence workspace. It collects documents, web pages, search results, transcripts and datasets into a persistent project, keeps every answer tied to the source it came from, and turns that accumulated material into reports, datasets and other deliverables — instead of losing it at the end of a chat.
The tools need no FlexContext account or subscription. Every tool runs in your browser, including the TTS studio, so there is no per-use cost.
No. Data and document tools process files in your browser, and the TTS studio generates speech in your browser too; its voice model is downloaded once from Hugging Face. Voice recipes are saved on this device.
A chat assistant starts from nothing each time and decides for itself what context to use. FlexContext is built the other way round: your sources persist across sessions, you control exactly what the model is given, and every claim carries a citation that opens the original document at the passage it came from.
Not yet. The product is not open, and a signup form implying otherwise would be dishonest. The tools are what is on offer today.
They are the same operations the product runs internally — chunking, retrieval scoring, token accounting, extraction, profiling. Giving them away is a more honest preview than a mockup, and it is useful to people whether or not the product ever ships to them.