LoRA-Studio is a local workflow manager for Stable Diffusion LoRA development, with a focus on SDXL / SD1.5 character and illustration LoRA iteration.
It does not try to replace creative judgment. Instead, it keeps datasets, training jobs, validation runs, candidate reviews, optimizer recipes, and final LoRA selection in one reproducible workflow.
Screenshots are captured from sanitized English demo views for OSS submission. Labels and sample data may differ slightly from a local development workspace.
- Project-based LoRA experiment tracking
- Dataset registration, rescanning, trigger checks, and version snapshots
- Training Job creation, preparation, execution, stop, clone, and archive
- Recipe v2 / Optimizer Master with Step Estimator and Compatibility Check
- LoRA-C3Lier recipes for sd-scripts
networks.lorawithconv_dim/conv_alpha - Post-training Review Automation and Candidate Standard Comparison
- Review Matrix and human review fields for candidate epoch selection
- Validation Run and Weight Calibration Pipeline for adopted LoRAs
- OpenCLIP / Machine Review Assist and Reference Sets
- Retry Signal Summary and Recommendation Engine separation
- Runtime storage settings and cleanup support for large generated artifacts
- Gradual Japanese / English i18n for screenshots and OSS-facing UI
- Create a Project for one LoRA creation effort.
- Register or rescan the dataset and check captions / trigger consistency.
- Create a Dataset Version before training.
- Create a Training Job using Recipe Wizard or a legacy preset.
- Prepare files, review preflight, then run training through sd-scripts.
- Use Review Session / Candidate Review to choose the candidate epoch.
- Adopt the LoRA output and run Weight Calibration / Validation.
- Apply the recommended weight range to the LoRA Profile.
- Export, archive, or clean up large unused outputs.
Install app dependencies:
powershell -ExecutionPolicy Bypass -File .\scripts\setup_app.ps1Start LoRA-Studio:
start_lora_studio.batOpen:
http://127.0.0.1:8768
Set up the verified sd-scripts environment when needed:
powershell -ExecutionPolicy Bypass -File .\scripts\setup_sd_scripts.ps1 -ReleaseTag v0.10.5 -CudaProfile cu128 -MixedPrecision bf16Create a sanitized demo database for README, documentation, and OSS submission screenshots:
python scripts/create_demo_db.py --output demo/demo.sqliteStart LoRA-Studio against the demo database in read-only demo mode:
python start_lora_studio.py --db demo/demo.sqlite --demo --no-browserOpen the English UI for screenshots:
http://127.0.0.1:8768/?lang=en
Demo mode uses only synthetic project names, datasets, images, reports, and paths. Training, generation, deletion, and other write actions are blocked. Generated demo runtime data and screenshots are ignored by Git. If Playwright is available, screenshots can be captured with:
python scripts/capture_demo_screenshots.py --base-url http://127.0.0.1:8768 --db demo/demo.sqlite- Japanese documentation index
- Japanese README
- English detailed documentation will be split under
docs/over time.
Current release: v0.5.5-beta Development phase: Phase 12.5
The core workflow is operational and used for local LoRA production, but APIs, screen flows, and recipe catalogs may still change during the beta period.
- Windows local workflow
- Python virtual environment created by
scripts/setup_app.ps1 - SQLite application database
- kohya-ss/sd-scripts integration, verified against
v0.10.5for the beta workflow - NVIDIA GPU environment appropriate for SDXL / SD1.5 LoRA training
- Machine Review Assist is advisory. Human visual review remains the final decision source for identity, costume details, style, and adoption.
- Smoke Test and Mini Pilot statuses confirm startup or short practical runs; they do not guarantee final LoRA quality.
- LoRA-C3Lier is treated as the sd-scripts standard LoRA extension for 3x3
Conv2d layers via
networks.loraandconv_dim/conv_alpha. LyCORIS LoCon is a separate future network type. - Keep large model files,
runs,exports, logs, and embedding caches outside OneDrive or other synchronized folders when possible. - sd-scripts logs, generated commands, raw args, and tracebacks are intentionally not translated by the i18n layer.
See LICENSE.




