lattedit

Contact and support

Email cneuralnets@gmail.com for lattedit support, API questions, and security reports.

Bug reports

Include the browser and operating system, the compiler you selected, the smallest LaTeX example that reproduces the problem, and the relevant log excerpt. Remove private document text, credentials, personal information, unpublished research, and any file you do not want to disclose.

API and integration questions

Read the developer guide and OpenAPI contract first. If the documented response does not match the live endpoint, email the request method, path, HTTP status, response headers, and a redacted request body. Never send an account token, Supabase credential, browser database, or document containing sensitive material.

Security reports

Email the affected URL, expected boundary, observed behavior, and a safe reproduction. Do not access another user's data, disrupt the shared compiler, or include secrets in the report. Reports involving exposed files, compilation isolation, or access controls receive priority.

Service status and support

The compiler health endpoint is available at /api/v1/health. The free Render instance can take time to wake after inactivity. If the editor is useful, the optional support page contributes toward hosting; support does not buy preferential access or change the service terms.