Skip to main content
← All insights

Beyties / Listing photos and video

Beyties property media processing

Beyties property media processing is a workflow that separates uploaded sources from web display files. Beyties has photo and video conversion code in the existing application documented in the 24 October 2026 review. Beyties’ output preparation preserves photo proportions and treats video as a separate encoding task. Large property shoot files create resizing and preparation work before an agency can publish a listing. Output quality depends on source detail and compression settings, so a smaller file does not guarantee the same visual result. The reviewed default limits are 100 mebibytes (MiB) for photos and 400 MiB for videos, with a separate five-minute video limit. The 24 October review records that the new listing editor’s complete optimized-media path remains unfinished.

Which files does Beyties property media processing accept?

Beyties property media processing has separate checks for file size, image dimensions and video duration in the code reviewed on 24 October 2026. The reviewed upload policy sets a default photo limit of 100 mebibytes (MiB) and a video limit of 400 MiB. The video duration limit is five minutes, while the photo size limit can vary by organization setting.

A file below the byte limit still needs a supported format and valid dimensions. A hypothetical 90 MiB photograph therefore passes only the default size comparison. The photograph still fails acceptance when the actual format or pixel dimensions breach the applicable rules. The example describes a check, not a successful customer upload.

The reviewed upload flow sends a file to a supplied upload address. The server checks the received file against the expected record before processing. The processing checks inspect the photograph’s actual format and dimensions rather than trusting the filename extension. Passing an upload check does not establish that display outputs exist.

How does Beyties choose property photo sizes?

An illustrated property photograph branches into a listing card and a larger gallery view.
One upload, different display needs. The source and the files shown to visitors serve different jobs. Conceptual illustration.

Beyties property photo processing prepares WebP image outputs with width ceilings of 400, 800, 1,200 and 2,565 pixels in the reviewed standard profiles. The output selection depends on source dimensions and preserves the photograph’s proportions. A smaller source is not enlarged to fill a larger profile.

The source is the uploaded file. The display output is a separately prepared version for a card, gallery or larger view. Preparing one small card image before upload can remove detail needed in a gallery. Sending the large source for every card increases the data transferred for a small image.

For example, a hypothetical source that is 800 pixels wide cannot supply 2,565 pixels of captured detail. An 800-pixel source does not become a detailed zoom photograph merely because a zoom profile exists. The example follows the reviewed no-enlargement rule and does not report a measured image-quality result.

The same illustrated room is shown in three proportionally sized frames.
Different resolutions preserve the composition. A larger frame cannot restore detail missing from a small source.

The Beyties code review of 24 October 2026 records a medium output as the existing card component’s default. The large-image viewer prefers the zoom output when a zoom output exists. The output actually delivered also depends on the available candidates and display conditions. A medium default is not proof that every browser receives the same file.

Preparing display sizes in the processing layer reduces the number of separate files an agency needs to prepare manually. The preparation benefit depends on connecting upload, processing and display. Higher-resolution output also depends on source and account conditions. The code review does not support an automatic 4K output promise for every upload.

Can smaller property photos preserve useful detail?

Smaller property photos preserve useful detail only to the extent supported by the source and compression settings. The reviewed Beyties profiles use different settings for small previews and larger outputs. A smaller file is not evidence of lossless processing or an identical visual result.

Google describes WebP as an image format with lossy and lossless compression in its WebP documentation. Google distinguishes the two compression modes. Google’s format description does not establish which quality setting a particular property website uses.

Compression quality is the amount of visual information retained during encoding. Image fidelity is the visible detail that remains in the output. The reviewed compression settings represent a file-size and quality choice, not a guaranteed percentage saving.

For example, a room photograph can contain thin window frames, fine interior lines and dark corners. A useful comparison inspects the same details in the source and output at the same display size. A smaller file that obscures the window frame fails that visual check even when the upload succeeds.

The 24 October 2026 review does not include a measured source-and-output quality comparison. The absence of a measured comparison prevents a promise of equal quality or a universal reduction percentage. A concrete follow-up needs the permitted source file, output file, dimensions, byte sizes and matching viewing conditions.

Does Beyties keep the original property photograph?

Beyties stores the uploaded source separately from generated web outputs in the reviewed processing path. The uploaded source is the file sent to the server, which can differ from the camera original. The reviewed separation is not a promise of permanent archival storage.

An edited photograph remains an edited source when someone selects that photograph for upload. An upload interface can also send an enhanced version instead of the initially selected file. For example, an agency that selects a cropped room photo uploads the crop, not the discarded edges of the camera image. Keeping the camera archive and retaining the uploaded source are different tasks.

The photo processing review records that generated outputs omit Exchangeable Image File Format (EXIF) metadata and Global Positioning System (GPS) location metadata. Removing embedded location metadata reduces the chance of publishing that hidden information. Metadata removal does not hide an address sign or a person visible within the photograph.

A hypothetical exterior photograph illustrates the distinction. The output can omit embedded location coordinates while still displaying a readable street number. Inspect the visible image separately from its embedded metadata.

How does Beyties prepare property videos?

A strip of property video leads to a playable video and a separate still preview.
Video and its cover are separate outputs. MP4 carries playback media, while a WebP poster comes from the first frame.

Beyties property video processing produces Moving Picture Experts Group (MPEG)-4 Part 14 (MP4) files with H.264 video, Advanced Audio Coding (AAC) audio when present, and separate WebP posters in the reviewed code. MP4 is the media container, and H.264 is the video coding format. The processor re-encodes the media instead of changing the filename extension.

The Beyties media processing review dated 24 October 2026 records three video profile bounds. Profile bounds describe the box into which the source fits. Source proportions and dimensions determine the actual output, so every video does not produce three full-size files.

Video profile Width and height bounds Shared constraint
Medium 854 × 480 pixels Preserve proportions without enlarging the source
Large 1,920 × 1,080 pixels Preserve proportions without enlarging the source
Zoom 2,560 × 1,440 pixels Preserve proportions without enlarging the source

For example, a portrait walkthrough does not become a stretched landscape video. The processor fits the portrait within the profile bounds while retaining the portrait proportions. A source smaller than the next profile remains limited by its captured detail.

Each generated video output receives a poster extracted from the first frame. A first frame that shows a dark corridor gives the poster a dark corridor too. The extraction creates a cover image, not a judgment that the cover presents the property well.

The reviewed MP4 preparation places playback information near the beginning of the file. The placement supports web delivery but does not establish a measured startup time on a visitor’s connection. Separate video outputs also do not establish adaptive streaming that changes quality with network speed.

How can an agency check processed property media?

An agency can check processed property media through three stages covering the source, generated output and visitor-facing file. Each stage answers a different readiness question. A completed upload answers only whether transfer completed, not whether the display result is usable.

The checks follow a fixed order. First, source inspection establishes whether enough usable detail exists. Second, output inspection checks the conversion. Third, visitor-view inspection checks delivery of an appropriate available output.

  1. Inspect the source photograph at the intended viewing size.
  2. Inspect the generated photograph or video for conversion defects.
  3. Inspect the visitor-facing file in the card and gallery views.

The first check includes sharpness and source detail. The second check includes photo orientation, video playback and poster choice. The third check compares the small card with the larger view instead of assuming both should download the same file.

For example, a photograph can finish uploading while a required gallery output fails to generate. The successful transfer does not make the gallery output usable. The reviewed processing path tracks transfer and processing separately and checks usable outputs before treating the media as ready.

Record the failed stage when processing fails. A missing source, rejected format and failed output generation require different investigation. The 24 October 2026 inspection establishes code paths for status and errors, not a guarantee that every failure recovers automatically.

Is Beyties property media processing ready in the new listing editor?

The 24 October 2026 implementation review records an unfinished path from the new listing editor to the visitor-facing optimized gallery. The review also records photo and video conversion code in the existing Beyties application. Existing conversion code does not prove that the new listing workflow exposes the same capabilities.

Beyties is a property software product under development in closed beta. Beyties has an existing pilot in the recorded product status. Beyties’ beta scope does not establish that every described processing capability is available in a new listing workflow.

For example, accepting a photo in a new listing form does not demonstrate that a visitor receives a generated gallery version. The complete check follows the uploaded file through processing to the actual gallery request. A successful upload alone leaves processing and visitor delivery unverified.

Beyties’ public product page provides the product background and existing agency website examples. The broader product context appears on the Beyties page. The public examples do not replace a check of the particular media path being discussed.

A useful agency discussion starts with one preparation problem. Record the file type and approximate size. Identify the step that requires repeated manual work. A large photographic shoot and a short property walkthrough can need different processing even when both belong to the same listing.

Does Beyties enlarge a small property photo?

The reviewed photo processing does not enlarge a small source merely to fill a larger profile. More output pixels cannot recover detail absent from the source.

Does a WebP file prove lossless compression?

A WebP file does not by itself prove lossless compression. WebP supports different compression modes, and the selected mode and settings determine the processing.

Does a completed upload mean property media is ready?

A completed upload does not prove that usable display outputs exist. Transfer, conversion and visitor delivery require separate checks.

Does the media review prove a faster property website?

The media review does not contain a measured visitor-speed improvement. Output preparation and appropriate file selection describe implementation choices, not a verified performance gain.