Single file pure HTML tool for viewing LoRA metadata that can be run locally on your web browser without the need of installation or internet connectivity.
To use, just extract the attached Zip and open the extracted HTML file with the web browser of your choice. Alternatively, you can use the version hosted on Github: https://xypher7.github.io/lora-metadata-viewer
Not thoroughly tested, but should work with most modern web browsers. To be honest I didn't really intend to share this so its kind of low effort and pretty basic. However, I decided to post it since others might find it useful too. I don't really plan to update this as it already does what I need, plus I want to keep it as simple and lightweight as possible. Though suggestions are always welcome.
Github repository URL: https://github.com/Xypher7/lora-metadata-viewer
Features:
Configurable metadata summary
CivitAI resource lookup. (Requires internet connection)
Configurable training tag summary
Edit or remove metadata in the Safetensors file
Doro :3
Description
1.4.3
Integrated storage API for saving user settings
1.4.4
Added training time calculation
1.5
Minor styling changes
Added editor validations to prevent saving the file with errors that might break the LoRA
Code cleanup
FAQ
Comments (8)
useful, thank you :)
This rocks. Thanks so much =)
useful, thank you :)
I'm completely tired of trying to fix the Hash of my lora... Civitai reports one Hash "Auto3" and Forge reports another. I erased any hash on the file metadata and it is still mismatched after I upload the new file on Civitai. I'm getting insane trying to fix this.
If I don't any uploaded image that is not done directly on the lora page is not recognized.
Anyone experiencing this?
Yep its been a pain. Has to do with how forge/automatic111 calculates Auto3 vs how CivitAI calculates it.
Just posted a tool to try and fix that exact issue by changing the image metadata to show the SHA256 (which seems to be the same across both applications). However it fixes things after the images are already generated instead of fixing the root issue.
Honestly wish that Forge/automatic would just let you pick what hash you want to use. Someone much smarter than me would have to figure that out.
@Pengu997 Yeah I've experienced that as well. For Flux trained with ai toolkit there is an eve worse problem that it writes a random hash to the LoRA: https://github.com/ostris/ai-toolkit/issues/130
Actually you could try to use the tool from that guy on the bug report, maybe it will fix the problem for non flux loras as well.
@diogod Man that really helps! Took a bit of tinkering but I managed to get that working to fix all my lora.
@Pengu997 good to know! Maybe write a quick step by step of your tinkering there or here to help other people. I know that I'll eventually need it. lol