Zero-Server Processing: Your images and JSON never leave your device. All logic is executed client-side via your browser's RAM.
1. Upload KoboldAI JSON
Technical Documentation: Mapping Legacy Backend Saves to Classical Prefixes
The migration from **KoboldAI** to **Pygmalion** JSON represents a transition between two of the AI roleplay community's most important foundational data models. While KoboldAI's format is designed primarily to preserve the context state of an inference session, the Pygmalion standard serves as a generalized, prefix-heavy bridge for classic frontends and early inference tools.
1. Field Mapping
Pygmalion characters utilize explicit key prefixes like char_name, char_persona, and world_scenario. KoboldAI JSON files (typically found in legacy Lite frontends) utilize a more traditional flat structure with keys like description and scenario. Our converter reads the fields it recognizes in the KoboldAI data and copies each one to the matching Pygmalion field, so your text arrives as written.
2. Dialogue and Example Text
Classic Pygmalion-compatible models perform best with clean, narrative-driven dialogue examples. KoboldAI save files are often formatted for raw text completion, which can include messy tokens or inconsistent formatting. Beyond the changes listed under "What this converter changes", your descriptions and dialogue are carried over exactly as written.
3. Context and Identity Fields
Both KoboldAI and Pygmalion users rely heavily on the character's backstory and scenario. Our tool ensures that the core narrative intent of your Kobold characters is meticulously preserved in the world_scenario and char_persona blocks of the new Pygmalion JSON. This provides classic inference tools with the best possible roadmap for generating relevant, character-aligned responses that stay true to the original creator's vision.
4. Privacy and the "Zero-Server" Mandate
Just like the foundational tools we bridge, our converter prioritizes privacy. By using a "Zero-Server" architecture, we perform the entire schema translation within your browser's RAM via JavaScript. Your character files, intimate details, and creative backstories are never transmitted across the open web. This ensures that you maintain absolute control over your digital assets as you move them between the industry's most established local AI standards.
5. Future-Proofing Legacy Characters
By outputting a standardized Pygmalion JSON, we ensure that your KoboldAI characters remain compatible with a vast array of legacy tools and specialized roleplay frontends. This conversion process isn't just about moving a file; it's about preserving your creative history and ensuring your digital characters remain accessible, editable, and compatible with the broader AI ecosystem, regardless of the evolving landscape of inference technology.
