Confused about the structure of a JS/TS or Python file? Upload one file and we return a deterministic ProjectMap of blocks (imports, exports, types, functions, classes/methods) plus edges (best-effort calls).
Deterministic in, deterministic out. No AI-hallucinated structure.
What you send → what you get
Single-file extraction returns deterministic structure you can render anywhere: blocks + edges.
// input: a single file
import { normalizeHeaders } from "./headers";
export const X = 1;
export function normalizeRequest(req) {
const headers = normalizeHeaders(req.headers);
const ip = extractClientIp(req, headers);
return { headers, ip };
}
// output: ProjectMap
// blocks: IMPORT | EXPORT_CONST | TYPE | INTERFACE | FUNCTION | CLASS | METHOD
// edges: CALLS (best-effort)
Designed to feel like HTML/CSS: see the structure first, then learn the details.
More details provided on the Docs
FileFig is designed to be safe by default:
When analytics are added, they will be metadata-only (counts, latency), never raw code.
Use single-file FileFig for learning and personal work. If you want to embed FileFig into an app, a SaaS product, a commercial workflow, or resell it as a feature, use a commercial plan.
Planned: Plus adds the FileFig Viewer and export formats for professional artifacts.
(Pricing page coming soon.)
I’m an inventor and systems architect building deterministic, privacy-first infrastructure tools. FileFig is structure-first code comprehension.