Skip to main content

Changelog

Follow new updates and improvements to Venice.ai.

Venice.Ai Change Log - September 16th - October 20th, 2025

Thanks for your patience in-between release notes — the Venice team has been hard at work over the last month at our all-hands offsite preparing for Venice V2 and shipping our most requested feature to date, Venice Video.

Moving forward, release notes will move to a bi-weekly cadence.

Venice Video

Video generation is now live on Venice for all users.

You can create videos on Venice using both text-to-video and image-to-video generation. This release brings state-of-the-art video generation models to our platform including Sora 2 and Veo 3.1.

You can learn all about this offering here.

Venice Support Bot

  • Launched AI-powered Venice Support Bot for instant, 24/7 assistance directly in the UI.

  • Bot pulls real-time information from venice.ai/faqs to provide up-to-date answers to common questions.

  • Users can escalate to create support tickets with context when additional help is needed beyond FAQ responses.

  • Available in English, Spanish, and German.

  • Accessible via bottom-right corner (desktop) or chat history drawer (mobile browser/PWA).

App

  • Launched Image “Remix Mode” - This is like regenerate, but uses AI to modify the original prompt. This provides an avenue to explore image generation prompts in more depth.

  • Added “Spotlight Search” to the UI. Press Command+K on a Mac or Control+K on Windows to open the conversation search.

  • Add a toggle in the Preferences to control the behavior of the “Enter” key when editing a prompt.

Characters

  • Venice has launched a “context summarizer” feature which should improve the LLMs understanding of important events and context in longer character conversations.

API

  • Added 3 new models in “beta” for users to experiment with:

    • Hermes Llama 3.1 405b

    • Qwen 3 Next 80b

    • Qwen 3 Coder 480b

  • Retired “Legacy Diem” (previously known as VCU). All inference through the API is now billed either through staked tokenized Diem or USD.

Venice.ai Change Log - August 26 - September 15th, 2025

API Pricing Updates

We’ve rolled out pricing drops across the Venice API’s specialized chat models (input/output):

  • Venice Small (qwen3-4b) → $0.05 / $0.15 (was $0.15 / $0.60)

  • Venice Uncensored (venice-uncensored) → $0.20 / $0.90 (was $0.50 / $2.00

  • Venice Large (qwen3-235b 2507 thinking and instruct) → $0.90 / $4.50 (was $1.50 / $6.00)

Build more, pay less. See the full pricing page: https://docs.venice.ai/overview/pricing

Qwen Image Performance

We have updated Qwen Image and fit a Lightning LoRA to it. Few changes:

  • Generations should run in about 1/2 the time as plain QI

  • As per recommendation from LoRA authors, we have pinned the CFG and Steps in the backend to 1 and 8 respectively.

App

  • Fixed pinch to zoom when the photo viewer is open.

  • Made additional improvements to LaTeX rendering used for mathematical equations.  

  • Fixed copy action not properly including in-painted / edited images.

  • Changed default for new API keys to “inference only” keys vs. “admin” keys.

  • Migrated to Qwen Edit as the default image editing / in-painting model.

  • Updated to latest version of Wallet Connect to improve wallet linking user experience.

  • Updated execution timer to reflect all images when generating multiple variants.

  • Improved rendering when printing text chats.

  • Improved auto model routing to direct anime related prompt to anime optimized models.

Social Feed

  • Updated social feed rendering to improve rendering of non-square aspect ratio photos.

  • Added a Download item to post share menus so users can save post images.

  • Added a “My Posts” tab to the social feed navigation.

API

  • Added an optional strict boolean on tool parameters to enable stricter parameter validation for tool calls.

  • Added model deprecation headers (x-venice-model-deprecation-warning and x-venice-model-deprecation-date) to API endpoints.

  • Added photoUrl parameter to character data returned from the API.

  • Added an API route to get details on a specific character. API docs have been updated.

  • Added support for multiple image generations via the API in a single request via the variants parameter. 

Venice.ai Change Log - August 19th - August 25th, 2025

Today’s cover art can be found on the Venice Social feed.

Web App Updates

  • Enhanced chat search across conversation titles, message content, and attachment names.

Tokenized DIEM Launched on Wednesday, August 20th

Last Wednesday, Venice launched support for Tokenized DIEM, including a new token dashboard design. Full details of the launch can be found here: https://venice.ai/blog/7-days-to-diem

Upcoming API Model Retirements

Venice has been steadily adding new models, and as users adopt them, we begin phasing out older ones with lower usage. A few models are scheduled for retirement, each with a stronger recommended replacement. Deprecation warnings will appear in your API responses when using these models until the sunset dates listed below.

You can see all the details about our deprecation policy in our Deprecations docs. Please check this page to understand:

  • Our lifecycle policy (when and why models get retired)

  • How deprecation warnings work in API responses

  • What happens after sunset dates

  • The live Deprecation Tracker (always up to date)

Models scheduled for deprecation → Recommended replacements:

Removal date: Sep 22, 2025
deepseek-r1-671b → qwen3-235b
llama-3.1-405b → qwen3-235b
dolphin-2.9.2-qwen2-72b → venice-uncensored
qwen-2.5-vl → mistral-31-24b
qwen-2.5-qwq-32b → qwen3-235b (with disable_thinking=true)
qwen-2.5-coder-32b → qwen3-235b
deepseek-coder-v2-lite → qwen3-235b
pony-realism → lustify-sdxl
stable-diffusion-3.5 → qwen-image

Removal date: Oct 22, 2025
flux-dev → qwen-image
flux-dev-uncensored → lustify-sdxl

Calls to these models will keep working until sunset, but with a deprecation warning. After sunset, direct calls to these IDs won’t return results unless you're using them via traits. We highly recommend using traits (default_code, default_vision, default_reasoning, etc.) since they always map to supported models.

Earlier updates