Smartgit License File Info

A SmartGit license file is an essential document used to activate and register a copy of the graphical Git client. Key Licensing Details Registration

: You must have a valid license file to register a new copy of the software; older, expired files will not work.

: Upon a successful subscription payment, the latest license file is sent via Automatic Updates

: SmartGit periodically checks for updated subscription licenses toward the end of a period and automatically downloads them if the software has internet access. Non-Commercial Use

: A free license is available for personal, non-commercial use, which can be selected during the initial installation. Management and Troubleshooting Trial Period smartgit license file

: If a commercial license is accidentally selected, a 30-day trial begins. After it expires, the software requires a valid license file to function. License Reset

: Users wishing to switch back to a free non-commercial license after a trial may need to manually delete specific system folders to reset the license status. Proxy Settings

: For automatic updates to function, SmartGit must have internet access, which may require manual proxy configuration in the application's preferences. a license file or where to find the license directory on your operating system? Pricing | SmartGit

Part 4: Converting a Non-Commercial or Evaluation License

Many developers start with a free non-commercial license but later need commercial features. SmartGit does not "upgrade" the license in place; you must replace the file. A SmartGit license file is an essential document

Steps to switch license type:

1. Open SmartGit → Help → License.
2. Click "Remove License".
3. SmartGit will revert to evaluation mode.
4. Now click "Install License File" and select your commercial smartgit.license.
5. Verify the new expiration date and features (e.g., GitHub integration, SVN support).

Warning: After removing a license, SmartGit may show a nag screen. This is normal. Simply install the new file.

Common user workflows

• Installing license file: place provided file into SmartGit’s license directory or use the GUI activation dialog.
• Moving to a new machine: deactivate/transfer via vendor portal or request new license tied to new machine.
• Renewing subscription: vendor sends updated license file or SmartGit auto-updates license via online validation.
• Using free/non-commercial license: register with the vendor if required, obtain a free license, place it or activate in-app.

5. Troubleshooting Common Issues

"License file is invalid"

• Ensure you are trying to load the correct file type. It should be an XML-based file provided by Syntevo, not a generic text file.
• Check if you are using a license for a newer major version on an older installation (e.g., using a SmartGit 23 license on SmartGit 21). You may need to update the application to match the license version.

"Evaluation period has expired"

• If you have purchased a license but see this message, the software has not successfully loaded the license file. Try the Manual Method (Method B) above to force the software to read the file from the settings directory.

"Non-Commercial Use" prompts keep appearing

• If you have a paid license but are still getting prompts for Non-Commercial use, ensure you selected "Use Commercial License" in the setup wizard and that your license file was successfully imported.

How activation works (high-level)

1. User purchases license or requests free non-commercial license.
2. Vendor issues either a license file or an activation key tied to account/email.
3. SmartGit verifies license signature locally; for online activation, SmartGit contacts vendor servers to validate and fetch license data.
4. License unlocks paid features; expiration or subscription cancelation disables them.

1. What is the SmartGit license file?

SmartGit (by SyntEvo) requires a license file for:

• Commercial use (after the evaluation period)
• Proprietary features (e.g., GitHub pull requests, Git LFS, JIRA integration)

The license file contains encrypted licensing information bound to a specific user/email or a floating license server.