Editorial standards

The guides and reference pages on this site are written by the engineers who build and maintain MediaDocks. We publish under a collective byline — MediaDocks Engineering Team — rather than attributing articles to a named individual.

That is a deliberate choice, and worth being plain about. It is common practice to invent a plausible-sounding author with a stock photograph and an impressive biography in order to satisfy a search-quality checklist. We think a fabricated expert is a worse signal than an honest collective one, so we do not do it. What you can verify instead is the substance: the technical claims below are checkable against the tools themselves, and the limits we document are the limits you will actually hit.

Anything we state about what MediaDocks does is checked against the running pipeline rather than written from memory. When a page says the resolution ladder is read from the source, that it muxes DASH streams with FFmpeg, or that a resolved link expires after thirty minutes, those statements correspond to actual behaviour and actual configuration values, and they are updated when the implementation changes.

Claims about formats and codecs that are not specific to our service — compression ratios, browser support, container capabilities — come from the specifications and from the maintainers' own documentation. Where a figure is a range or an approximation, we write it as one. A number presented without qualification is a number we are willing to defend.

The scope sections on each platform page are tested against live public links instead of assumed from a platform's API documentation, which is why those pages are specific about which link shapes fail. A downloader that claims universal coverage and then fails silently wastes more of your time than one that tells you the truth up front.

We do not advertise capabilities the software does not have. MediaDocks cannot reach private accounts, age-gated videos, paywalled media or DRM-protected streams, and no page on this site suggests otherwise — including the pages that would get more traffic if they did.

We do not present a thumbnail as though it were a video, pad a resolution list with upscaled rungs that add file size and no detail, or describe an MP3 as higher quality than the source track it was made from. Each of those is a small deception that makes a product demo look better and makes the actual result worse.

We also try not to overstate the AI features. Transcription accuracy is high on clean audio and visibly worse on crosstalk, music and heavy reverb, and we say so on the pages that sell it. A transcript from this or any other service is a strong first draft, not a certified record.

AI tooling is used as a drafting and editing aid in producing this material, in the same way a spell-checker or a reference lookup is. It is not used to mass-produce articles on topics nobody on the team understands, and nothing is published without an engineer reading it against the behaviour it describes and signing off on the technical content.

The distinction we care about is not whether a machine touched the draft but whether a person is accountable for the claims. On every page here, one is.

Every guide carries a published date and a last-updated date, and the updated date moves when the substance changes rather than on a schedule designed to look fresh. Read-time estimates are computed from the article body, so they cannot drift away from the text as it is edited.

If you find an error, tell us through the contact page and we will fix it. Factual corrections to a technical claim are made in place, and where a correction changes the practical advice we leave a note rather than quietly rewriting history. We would rather be corrected than consistent.

The guides exist to explain the formats and trade-offs people run into while using the tools, not to funnel readers toward a paid upgrade — there is no paid tier to upgrade to. Where an article links to one of our own tools, it is because the tool does the thing the article just described.

We take no payment for coverage, and there are no sponsored articles, affiliate placements or paid reviews anywhere on this site. If that ever changes, it will be disclosed on the page in question and here.