Ongoing topic · Compiled September 11, 2026
DeepSeek V4.1 Flash: images, tools and new prices
How can screenshots, error messages and long documents become material for AI work? Follow image understanding, tool integrations, price changes and the release timeline.

01Reading images
A screenshot can become part of the question
- Event screenshot
List the date, place and things to bring
- Lesson or work chart
Explain the largest change
- Error screenshot
Suggest what to check next
Suggested questions to use with your own images. Read the source ↗
DeepSeek V4.1 Flash reads images together with text and answers in text. Beyond describing a picture, the official guide lists reading screenshot text and analyzing charts. An event page, a lesson chart or an error screenshot can accompany a specific question.
Start with a specific question: which dates and places appear in an event screenshot, where a chart changes most, or what an error message means. The image preserves the details; the question tells the model what to look for.
- DeepSeek Vision guidePrimary sourceRead the full details.
Notes and further sources
The questions and workflows are suggested uses; this article does not present model outputs from BitShovel tests.
- DeepSeek V4.1 Flash model card ↗Primary sourceRead the full details.
02Working with tools
After reading, continue into the files
With tools attached, an answer can lead into the next step of a task. DeepSeek Harness asks users to configure a model and choose a workspace. It can read and edit files, run commands, delegate work and maintain a plan. A developer might begin by understanding an unfamiliar project, then continue into edits and checks.
This is where vision and coding meet: a screenshot explains what should change, while project files contain the implementation. Together, they can make a request clearer than a long verbal description of an interface. This is a suggested workflow; the connected tool performs the actual actions.
- DeepSeek Harness Web UI guidePrimary sourceRead the full details.
Notes and further sources
- Official DeepSeek Harness repository ↗Primary sourceRead the full details.
- DeepSeek Vision guide ↗Primary sourceRead the full details.
03Speed and usage
More reasoning can mean more output

Flash is designed for faster inference and higher throughput, but task duration also depends on input length, reasoning effort and tool interactions. Reasoning effort is adjustable. The technical report plots task scores alongside output usage: greater effort generally produces more output, while scores do not rise at every step.
Speed and cost become tangible in repeated revisions, long-document work and tasks with several steps. How much the model reads, reasons and writes accumulates across the whole job.
- Official DeepSeek V4.1 Flash releasePrimary sourceRead the full details.
Notes and further sources
- Official technical report, Figure 9 ↗Primary sourceRead the full details.
- DeepSeek V4.1 Flash model card ↗Primary sourceRead the full details.
04Cost
Frequent small tasks are easier to budget

The official USD API rates effective September 10 are $0.30 per million uncached input tokens, $0.006 for cached input and $1.20 for output at peak times. Off-peak rates are half. Peak periods are Monday–Friday, 09:00–12:00 and 14:00–18:00 Beijing time; other hours are off-peak.
If a request is billed for 100,000 uncached input tokens and 10,000 output tokens, the cost is $0.042 at peak rates or $0.021 off-peak. This is a calculation from published rates, not a fixed word count or task price. For batch document processing or repeated revisions, the bill depends on actual input and output usage.
- Current API pricingPrimary sourceRead the full details.
Notes and further sources
This example uses DeepSeek’s direct API USD rates. The Chinese edition uses the separately published CNY rates. Gateway, app subscription and tool charges are separate.
- Official DeepSeek V4.1 Flash release ↗Primary sourceRead the full details.
05Access
Start in an existing tool
The current direct DeepSeek API name is deepseek-flash. DeepSeek’s release also confirms integration with WorkBuddy, CodeBuddy and OpenCode. Existing users can check the models available in their tool and begin with a screenshot or project material. The connection between model and app determines which actions can follow an answer.
Vercel AI Gateway is another documented route. Its September 9 announcement describes requests combining text and images. The current model page uses deepseek/deepseek-v4.1-flash and provides playground and AI SDK entry points. Developers can start with their own material before integrating it into an application.
- Official DeepSeek V4.1 Flash releasePrimary sourceRead the full details.
Notes and further sources
Vercel requires gateway credentials and uses its own billing rules; DeepSeek Harness remains a developer preview. This research checked public sources and entry points without running model inference.
- Vercel integration announcement ↗Primary sourceRead the full details.
- Vercel current model and playground ↗Primary sourceRead the full details.
06Timeline
From the vision experiment to current access
From the early vision experiment to the released model and tool integrations, follow the key dates.
- Vision experiment reaches the API: V4 Flash Vision Exp provided an earlier API vision route; that old model has now been retired.
- Vercel announces integration: AI Gateway announced image-and-text requests and app integration. This is the Vercel announcement date, not DeepSeek’s official release date.
- V4.1 Flash officially released: DeepSeek released native image-and-text understanding and model weights. The API uses deepseek-flash; new pricing took effect at 12:00 Beijing time.
- Planned legacy-route change: from September 14 at 12:00 Beijing time, deepseek-v4-pro will route to V4.1 Flash until V4.1 Pro follows.
Notes and further sources
- September 10 release coverage →Earlier coverageOriginal coverage and publication date.
07What comes next
What we are following
- Which examples of image understanding, file reading and real tasks are worth seeing?
- Which everyday tools will adopt it, and how will using them change?
- How will pricing, speed and long-task performance evolve?