Convert Any File to FLV Online for Free
Build a deliberate FLV delivery file from selected readable media streams, with checked Flash Video tags, codecs, timestamps, metadata, and receiver support.
- Add a file Choose or drop it here
- Pick the format Change it whenever needed
- Download the result After conversion completes
Convert Any File to FLV Starts With Selecting Real Media Streams
“Any file” is not a technical source format. A readable input may contain one video stream, multiple cameras, alternate audio, subtitles, still images, data tracks, or no playable media at all. Before an FLV conversion, inspect the actual input and select the presentation: video stream, audio program, language, time range, display aspect, and any tracks intentionally omitted. Record codec/profile, dimensions, pixel format, frame timing, audio rate/channels, start offset, and duration. A filename suffix cannot establish those facts.
Decide whether a source can be remuxed only after checking its encoded streams against the intended FLV receiver. Ordinary conversion often means decoding source video/audio and producing new target streams. Re-encoding is a new lossy generation: it does not restore source detail, frames, color information, or audio bandwidth. Scaling, cropping, deinterlacing, frame-rate conversion, downmixing, loudness adjustment, trimming, and subtitle handling are separate choices that must be named.
Keep important originals. An FLV is normally a delivery derivative and may omit source-specific metadata, alternate tracks, chapters, location, edit structure, or access controls. It cannot decrypt protected content or grant permission to transform it. Test a short representative section before a long export, then compare the first event, a motion scene, a middle event, a seek, and the final seconds in the actual application that will receive the file.
The FLV Header Announces Tag Streams but Does Not Define Their Codecs
An FLV file begins with the signature bytes F, L, V, followed by a version and type flags. Adobe’s FLV specification defines an audio-present flag and a video-present flag; the header’s DataOffset normally has value 9 for FLV version 1. Those flags say whether the file contains audio and/or video tags. They do not prove that the selected codecs, video profile, dimensions, or audio configuration will decode in every player.
After the header, FLV is organized around tags. The useful tag types are audio, video, and script data. A tag header includes data size, timestamp, an extended-timestamp byte, and stream ID. The commonly used timestamp layout has a 24-bit low field plus an 8-bit extension, rather than an excuse to store arbitrary source timecodes. Create a monotonic presentation timeline from the selected source streams and validate it after muxing.
A valid header cannot repair a wrong input. If video was selected without its corresponding audio, or the source starts with an offset, the generated FLV needs an intentional output policy. Verify flags agree with the actual written tags and that a video-only result is deliberate rather than a failed audio conversion.
FLV Video Tags Need Matching AVC Configuration and Frame Timing
FLV video tags carry a frame/codec indicator and a video payload. For AVC/H.264 in FLV, the video payload distinguishes an AVC sequence header from NALU data and an end-of-sequence marker. The sequence header supplies the decoder configuration needed to interpret the later encoded access units. It is not safe to copy arbitrary source codec initialization bytes, rename a video stream, and assume an FLV player will understand it. Configuration, profile, level, pixel format, and coded frames must agree.
Choose a video codec path from the receiver’s real capability. FLV has legacy associations and modern browsers frequently have different support expectations from old Flash-oriented players. A target that says “FLV accepted” may still reject a particular AVC configuration, audio combination, resolution, or duration. Test the exact receiver, not just a permissive desktop decoder.
Preserve frame order and presentation timing. Variable-rate source media, reordered frames, and an edited start need a standards-aware encode/mux. Check first display, source-to-output scene order, a middle seek, a late seek, and end playback. A file that displays one first image is not necessarily synchronized or navigable.
AAC in FLV Requires an AudioSpecificConfig Before Raw AAC Packets
FLV’s audio tag begins with sound-format information. For AAC, the specification defines AAC packet type 0 as the AAC sequence header and packet type 1 as raw AAC data. The sequence header contains the MPEG-4 AudioSpecificConfig, whose audio object type and configuration identify characteristics such as sampling frequency and channels. The FLV header’s nominal AAC sound-rate and stereo flag are not the authoritative audio properties; the specification says Flash Player derives actual rate and channels from the AAC bitstream configuration.
That means an FLV writer must produce a correct initial configuration and then timestamp raw AAC access units correctly. It must not treat ADTS headers from a standalone AAC transport stream as though they were the same payload form, nor use an unknown source audio stream without an intentional decode/encode path. If the source has commentary, alternate languages, surround sound, or leading silence, select and document the actual target program.
AAC introduces coding delay and framing behavior. Compare audible first content, not just zero time, with the source. If the output has an offset or drift, inspect source selection, resampling, encoder delay, mux timestamps, and final duration. Raising a bitrate or sample rate cannot restore information missing from prior compressed sound.
AMF Script Metadata Is Descriptive, Not a Substitute for Media Validation
FLV script-data tags can contain Action Message Format (AMF) metadata. Common fields can describe duration, dimensions, frame rate, audio/video data rate, codec IDs, keyframe information, and whether streams are present. These fields can help a compatible tool discover a file, but they are not the primary video/audio decoder configuration and cannot cure bad timestamps, absent finalization, or incompatible coded media.
Write metadata from measured output values and only carry source facts that are known and appropriate. Do not invent a creator, location, capture date, rights claim, camera identity, or “universal compatibility” assertion. Source-specific track metadata, timed captions, rich edit information, and proprietary fields may need a separately preserved original or sidecar. Remove personal information not required for delivery.
Validate the generated FLV independently: inspect tags and configuration, then play it in the intended receiver. Check duration, selected tracks, orientation, start, a middle seek, a late seek, and final playback. The AMF duration value should agree with actual media behavior, but a metadata value alone is never acceptance evidence.
Source Decisions and FLV Output Checks Compared
| Concern | Input investigation | FLV result to test |
|---|---|---|
| Stream choice | Actual video/audio programs, language, range, and properties. | Correct header flags and intended written tag streams. |
| Video | Codec, profile, geometry, aspect, frame timing. | Compatible tag codec and valid AVC sequence configuration. |
| Audio | Codec, rate, channels, offsets, and selected program. | AAC sequence header plus correctly timed raw packets. |
| Timeline | Presentation events and variable timing. | Monotonic 24-bit-plus-extension tag timestamps. |
| Metadata | Known values and source data requiring separate retention. | Measured AMF facts only, with no invented context. |
| Acceptance | Required receiver and delivery purpose. | Start, seeks, A/V sync, and end playback in that receiver. |
Questions Before Converting Media to FLV
Can any file be renamed to FLV?
No. The source must yield readable media, and FLV needs its own header, tag framing, codec configuration, timestamps, and receiver-compatible encoded streams.
Does FLV support both audio and video?
Yes when its header flags and tag streams are written accordingly, but each selected stream still needs a codec and configuration the receiving player supports.
Why is AAC silent in an FLV?
Check the AudioSpecificConfig sequence header, selected audio program, raw AAC payload form, timestamps, and actual receiver support.
Will AMF metadata make an incompatible FLV play?
No. It describes the output but does not change the decoder requirements of its audio or video tags.
Should the original source be kept?
Yes. It can retain selected-out tracks, original codecs, metadata, edit structure, and higher-quality source data that an FLV delivery copy omits.
Before delivery, compare the file’s reported FLV tag inventory with the output you meant to make: whether audio and video flags are present, which codec configurations were written, the first and final tag timestamps, selected languages or channels, and the media duration. Inspecting these details helps distinguish an FLV container fault from a decoder-policy fault. A player that accepts older VP6 or MP3 material may not accept the target AVC/AAC configuration, even though both are called FLV.
Keep a concise conversion record with source identifiers, input stream inventory, selected tracks, output video/audio settings, resize or frame-rate policy, target receiver, and test outcome. When an output later fails, that record provides actionable evidence: determine whether it is an unsupported codec, an incorrect sequence header, a bad timestamp, an unfinalized end, or a source selection mistake. Without it, repeated conversions can silently create more lossy generations while never addressing the actual incompatibility.